In current code, we always map writable pfn for the read fault, in order
to support readonly memslot, we map writable pfn only if 'writable'
is not NULL
Signed-off-by: Xiao Guangrong
---
virt/kvm/kvm_main.c | 24 +++-
1 files changed, 23 insertions(+), 1 deletions(-)
diff
In the later patch, it indicates failure when we try to get a writable
pfn from the readonly memslot
Signed-off-by: Xiao Guangrong
---
include/linux/kvm_host.h |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
index
In the later patch, it indicates failure when we try to get a writable
hva from the readonly memslot
Signed-off-by: Xiao Guangrong
---
include/linux/kvm_host.h |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
index
Then, remove bad_hva and inline kvm_is_error_hva
Signed-off-by: Xiao Guangrong
---
include/linux/kvm_host.h |8 +++-
virt/kvm/kvm_main.c | 13 +
2 files changed, 8 insertions(+), 13 deletions(-)
diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
index
In current code, if we map a readonly memory space from host to guest
and the page is not currently mapped in the host, we will get a fault
pfn and async is not allowed, then the vm will crash
We introduce readonly memory region to map ROM/ROMD to the guest, read access
is happy for readonly
Introduce write_readonly_mem in mmio-exit-info to indicate this exit is
caused by write access on readonly memslot
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/x86.c | 23 ++-
include/linux/kvm.h |3 +++
include/linux/kvm_host.h |1 +
On 21/08/12 11:55, Linus Torvalds wrote:
> Read my -rc2 release notes.
Ahh, thanks (I'm not on LKML so didn't see those).
> TL;DR: I rejected big pull requests that didn't convince me. Make a
> damn good case for it, or send minimal fixes instead.
Can't argue with that!
> I'm tried of these
2012/8/20 Stephen Warren :
> On 08/18/2012 12:33 AM, Axel Lin wrote:
>> Add missing platform_get_drvdata() call in max8907_regulator_remove(), this
>> fixes below build warning:
>>
>> CC [M] drivers/regulator/max8907-regulator.o
>> drivers/regulator/max8907-regulator.c: In function
>>
On 08/20/2012 01:04 PM, Andreas Schwab wrote:
John Stultz writes:
Huh. Yea, that looks fine. And without the
__timekeeping_inject_sleeptime() call, the system resumed ok?
Yes, it does.
So I'm mostly still stumped on this. But I did find one possible related
bugfix that maybe you can
From: Jianguo Wu
Hi all,
I found following definition in include/linux/memory.h, in my IA64
platform, SECTION_SIZE_BITS is equal to 32, and MIN_MEMORY_BLOCK_SIZE will be 0.
#define MIN_MEMORY_BLOCK_SIZE (1 << SECTION_SIZE_BITS)
Because MIN_MEMORY_BLOCK_SIZE is
Dne Po 20. srpna 2012 08:38:10 wujianguo napsal(a):
> From: Jianguo Wu
>
> Hi all,
> I think zone->present_pages indicates pages that buddy system can
> management, it should be:
> zone->present_pages = spanned pages - absent pages - bootmem pages,
> but now:
>
Hi Tejun,
Today's linux-next merge of the workqueues tree got a conflict in
drivers/hid/hid-picolcd.c between commit fabdbf2fd22f ("HID: picoLCD:
split driver code") from the hid tree and commit 43829731dd37
("workqueue: deprecate flush[_delayed]_work_sync()") from the workqueues
tree.
The
From: Manoj Iyer
USB 3.0 devices show up as high-speed devices on powerup, after an
s3 cycle they are correctly recognized as SuperSpeed. At powerup
unconditionally switch the port to xHCI like we do when we resume
from suspend.
BugLink: http://bugs.launchpad.net/bugs/1000424
Test results:
From: Manoj Iyer
USB 3.0 devices show up as high-speed devices on powerup, after an
s3 cycle they are correctly recognized as SuperSpeed. At powerup
unconditionally switch the port to xHCI like we do when we resume
from suspend.
BugLink: http://bugs.launchpad.net/bugs/1000424
Signed-off-by:
From: Wei Yongjun
Since we will be removing items off the list using list_del() we need
to use a safer version of the list_for_each_entry() macro aptly named
list_for_each_entry_safe(). We should use the safe macro if the loop
involves deletions of items.
Signed-off-by: Wei Yongjun
---
From: Wei Yongjun
Since we will be removing items off the list using list_del() we need
to use a safer version of the list_for_each() macro aptly named
list_for_each_safe(). We should use the safe macro if the loop
involves deletions of items.
Signed-off-by: Wei Yongjun
---
From: Wei Yongjun
Since we will be removing items off the list using list_del() we need
to use a safer version of the list_for_each() macro aptly named
list_for_each_safe().
Signed-off-by: Wei Yongjun
---
drivers/vme/bridges/vme_tsi148.c | 10 +-
1 file changed, 5 insertions(+), 5
Bjorn Helgaas wrote on 2012-08-21:
> On Mon, Aug 20, 2012 at 10:10 AM, Bjorn Helgaas
> wrote:
>
>> So I'll try pulling your branch (I'll do something about the tsi721.c
>> stuff myself).
>
> I pulled this into
> git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git
> pci/jiang-pcie-cap
Hi Hein,
I have added linux-kernel list in cc as there might be other users of
this patch.
Also, please try to keep spear-devel list in cc for dw_dmac as we are using this
driver for SPEAr.
On Sun, Aug 19, 2012 at 9:36 PM, Hein Tibosch wrote:
> Hi Hans-Christian,
>
> Do you know to which list I
On Sat, Aug 18, 2012 at 07:57:07PM -0700, Andi Kleen wrote:
> From: Joe Mario
>
> Use KSYM_NAME_LEN to size identifier buffers, so that it can
> be easier increased.
>
> Cc: ana...@in.ibm.com
> Signed-off-by: Joe Mario
> Signed-off-by: Andi Kleen
Acked-by: Ananth N Mavinakayanahalli
> ---
On Mon, Aug 20, 2012 at 1:30 PM, Stephen Warren wrote:
> On 08/20/2012 12:22 PM, Tejun Heo wrote:
>> Hello,
>>
>> On Fri, Aug 17, 2012 at 04:10:52PM -0600, Stephen Warren wrote:
>>> I was considering extending the kernel command-line option
>>> root=PARTUUID= to also support MBR (NT disk
On Mon, 20 Aug 2012, Aristeu Rozanski wrote:
> On Mon, Aug 20, 2012 at 12:10:09AM -0700, Hugh Dickins wrote:
> > Yes, it looks nice to me. I might have preferred more as inlines in
> > the header file to lower the slight init/evict overhead, and I don't
> > see why __simple_xattr_set() isn't
Hi Al,
Today's linux-next merge of the signal tree got a conflict in
arch/alpha/kernel/process.c between commit 28d353d9891c ("alpha: take
kernel_execve() out of entry.S") from Linus' tree and commit 68f596a7a045
("alpha: rewrite kernel_execve in C") from the signal tree.
These appear to be the
On Thu, 9 Aug 2012 15:46:20 +0530, Amit Shah wrote:
> Hi,
>
> On (Tue) 24 Jul 2012 [11:36:57], Yoshihiro YUNOMAE wrote:
> > Hi All,
> >
> > The following patch set provides a low-overhead system for collecting kernel
> > tracing data of guests by a host in a virtualization environment.
>
> So
On (Tue) 21 Aug 2012 [11:47:16], Rusty Russell wrote:
> On Thu, 9 Aug 2012 15:46:20 +0530, Amit Shah wrote:
> > Hi,
> >
> > On (Tue) 24 Jul 2012 [11:36:57], Yoshihiro YUNOMAE wrote:
> > > Hi All,
> > >
> > > The following patch set provides a low-overhead system for collecting
> > > kernel
> >
On Sun, Aug 19, 2012 at 08:56:03PM -0700, Greg Kroah-Hartman wrote:
> From: Greg KH
>
> 3.0-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Daniel Vetter
>
> commit 0d8957c8a90bbb5d34fab9a304459448a5131e06 upstream.
>
> We may only
On Mon, 2012-08-20 at 16:20 -0700, Andrew Morton wrote:
> On Mon, 20 Aug 2012 11:30:59 +0200
> Eric Dumazet wrote:
>
> > On Mon, 2012-08-20 at 10:04 +0100, Mel Gorman wrote:
> >
> > > Can the following patch be tested please? It is reported to fix an fio
> > > regression that may be similar to
On (Thu) 09 Aug 2012 [21:30:29], Yoshihiro YUNOMAE wrote:
> Hi All,
>
> The following patch set provides a low-overhead system for collecting kernel
> tracing data of guests by a host in a virtualization environment.
ACK this series.
I ran it through the virtio-serial test suite, and there's no
2012/8/21, J. Bruce Fields :
> On Mon, Aug 20, 2012 at 01:19:51PM +0900, Namjae Jeon wrote:
>> 2012/8/18, OGAWA Hirofumi :
>> > Al Viro writes:
>> >
>> >> On Sat, Aug 18, 2012 at 05:41:39AM -0400, Namjae Jeon wrote:
>> >>> From: Namjae Jeon
>> >>>
>> >>> This patch-set eliminates the client side
Hi Kay,
I found that udev 182 doesn't response for the request_firmware in
module_probe path until 30sec later after the 'ADD' event of firmware
device, but no such problem in udev175, sounds like a regression of udev?
I find there was a related discussion in [1], so CC guys who discussed
2012/8/21, J. Bruce Fields :
> On Mon, Aug 20, 2012 at 12:00:04PM +1000, Dave Chinner wrote:
>> On Sun, Aug 19, 2012 at 10:57:24AM +0800, Fengguang Wu wrote:
>> > On Sat, Aug 18, 2012 at 05:50:02AM -0400, Namjae Jeon wrote:
>> > > From: Namjae Jeon
>> > >
>> > > This patch is based on suggestion
From: Wei WANG
1. Fix a bug that DMA out of SW-IOMMU space in Lenovo Thinkpad x121e
2. Tested by Borislav Petkov
Wei WANG (2):
drivers/mfd: Add realtek pcie card reader driver
drivers/mmc: Add realtek pcie sdmmc host driver
drivers/mfd/Kconfig |9 +
drivers/mfd/Makefile
From: Wei WANG
Realtek PCI-E SD/MMC card host driver is used to access SD/MMC card,
with the help of Realtek PCI-E card reader MFD driver.
Signed-off-by: Wei WANG
Reviewed-by: Arnd Bergmann
Tested-by: Borislav Petkov
---
drivers/mmc/host/Kconfig |7 +
drivers/mmc/host/Makefile
On Fri, Aug 17, 2012 at 12:34:11PM +0200, Sebastian Andrzej Siewior wrote:
> On 08/17/2012 12:30 PM, Andrzej Pietrasiewicz wrote:
> >>There is a separation between "setting myself up" and "seeing that a host
> >>wants to talk to me". You are a woman. And if you not done yet done you
> >ignore
>
On Sun, 2012-08-19 at 20:47 -0400, Theodore Ts'o wrote:
> On Mon, Aug 20, 2012 at 01:06:20AM +0200, Carlos Alberto Lopez Perez wrote:
> >
> > > I also seriously question the niche of people who want to use a thumb
> > > drive to transfer > 4GB files. Try it sometime and see what a painful
> > >
Hi Matthew,
After merging the drivers-x86 tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/platform/x86/asus-wmi.c: In function 'asus_new_rfkill':
drivers/platform/x86/asus-wmi.c:892:3: error: implicit declaration of function
'rfkill_set_led_trigger_name'
> * Rather than having to do the #ifdef here, I think it would be better
> if
> the PWM subsystem provided stub functions for pwm_request, pwm_config,
> pwm_enable, pwm_disable and pwm_free that do nothing, so you can in
> effect
> let the compiler optimize away the above code.
Thanks a lot
> > * Rather than having to do the #ifdef here, I think it would be
> better if
> > the PWM subsystem provided stub functions for pwm_request,
> pwm_config,
> > pwm_enable, pwm_disable and pwm_free that do nothing, so you can in
> effect
> > let the compiler optimize away the above code.
>
From: Jianguo Wu
Hi all,
When doing memory-hot-plug, We found node distance is wrong after
offline
a node in IA64 platform. For example system has 4 nodes:
node distances:
node 0 1 2 3
0: 10 21 21 32
1: 21 10 32 21
2: 21 32 10 21
3: 32 21 21 10
On Sat, 2012-08-18 at 17:45 -0700, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Fix kernel-doc warnings in kernel/sched/fair.c:
>
> Warning(kernel/sched/fair.c:3660): Excess function parameter 'cpus'
> description in 'update_sg_lb_stats'
> Warning(kernel/sched/fair.c:3806): Excess function
Hi Shmulik,
2012/8/19 Shmulik Ladkani :
> Hi Richard,
>
> On Fri, 17 Aug 2012 16:35:21 +0200 Richard Genoud
> wrote:
>> + /*
>> + * A value of 0 is forced to the default value to keep the same
>> + * behavior between ubiattach command and module parameter
>> + */
>
> Minor
> In net/caif/chnl_net.c::chnl_recv_cb() we call skb_header_pointer()
> which may return NULL, but we do not check for a NULL pointer before
> dereferencing it.
> This patch adds such a NULL check and properly free's allocated memory
> and return an error (-EINVAL) on failure - much better than
Hi,
The commit 154a7a7b2234 ("asus-wmi: update wlan LED through rfkill led trigger")
needs another patch which was submitted to rfkill, but still not be merged yet.
see https://patchwork.kernel.org/patch/1240091/
Sorry for leading to the problem.
Best regards,
AceLan Kao.
2012/8/20 Stephen
On Monday 20 August 2012, Kim, Milo wrote:
> > * I don't understand why you need the "if (rvdata->pwm) return 0;" case.
> > It's normally better to do the initialization exactly once from the
> > probe() function. You might want to return -EPROBE_DEFER if the pwm
> > source is not yet
On 08/19/2012 10:03 AM, Julia Lawall wrote:
> From: Julia Lawall
>
> It was forgotten to initialize ret to the result of calling
> snd_soc_dai_set_sysclk, unlike at the other calls in the same function.
>
> A simplified version of the semantic match that finds this problem is as
> follows:
On Sunday 19 August 2012 23:07:32 Raymond Jennings wrote:
> On Sun, 2012-08-19 at 20:47 -0400, Theodore Ts'o wrote:
> > On Mon, Aug 20, 2012 at 01:06:20AM +0200, Carlos Alberto Lopez Perez wrote:
> > >
> > > > I also seriously question the niche of people who want to use a thumb
> > > > drive to
Hi Artem,
2012/8/19 Artem Bityutskiy :
> Yeah, I wanted to make it 1..256 but forgot, will do now. 0..256 would
> need some more work to avoid division by 0.
Division by 0 is handled in the get_bad_peb_limit() function, I don't
see another dangerous place.
So, I think that we can change back the
> From: anish kumar
>
> Instead of "const char **supported_cable" it is better to have
> it as "const char *const *supported_cable".
>
> Signed-off-by: anish kumar
Could you please elaborate on why it's better?
(Is this fixing the using the standard naming issue Mark mentioned before?)
>From 152373a6262045d19023cf45de84ad3c69316a45 Mon Sep 17 00:00:00 2001
From: Jovi Zhang
Date: Mon, 20 Aug 2012 14:20:01 +0800
Subject: [PATCH] pstore: add missed platform_device_unregister
we need unregister platform device when module exit, add it.
Signed-off-by: Jovi Zhang
---
At 08/20/2012 02:21 PM, wujianguo Wrote:
> From: Jianguo Wu
>
> Hi all,
> When doing memory-hot-plug, We found node distance is wrong after
> offline
> a node in IA64 platform. For example system has 4 nodes:
> node distances:
> node 0 1 2 3
> 0: 10 21 21 32
> 1: 21 10
On Sat, 18 Aug 2012 19:56:23 -0700, Andi Kleen wrote:
> @@ -78,11 +78,13 @@ extern struct module __this_module;
>
> #else /* !CONFIG_MODULES... */
>
> -#define EXPORT_SYMBOL(sym)
> -#define EXPORT_SYMBOL_GPL(sym)
> -#define EXPORT_SYMBOL_GPL_FUTURE(sym)
> -#define EXPORT_UNUSED_SYMBOL(sym)
>
Hi Linus,
Please pull the latest fixes from the arm-soc tree. Since most patches
came in after I sent out the previous pull request but before -rc2, the
branch is based on the last commit you pulled from me, in case you are
wondering.
Arnd
The following changes since commit
On 08/19/2012 02:33 PM, Roland Stigge wrote:
On 17/08/12 11:42, Sebastian Andrzej Siewior wrote:
Some minor things:
- please use to_udc() in start then
- would it make sense to use platform_get_drvdata() in
lpc32xx_udc_shutdown() ?
- could you please remove struct usb_endpoint_descriptor
On Thu, 16 Aug 2012, Tejun Heo wrote:
> On Thu, Aug 16, 2012 at 01:44:54PM -0400, a...@redhat.com wrote:
> > From: Li Zefan
> >
> > Extract in-memory xattr APIs from tmpfs. Will be used by cgroup.
> >
> > $ size vmlinux.o
> >textdata bss dec hex filename
> > 4658782 880729
On Sat, Aug 18, 2012 at 09:01:52PM +0200, Wolfram Sang wrote:
>
> > > I thought to recall that busses which can be probed at runtime should
> > > not have nodes but should be probed. Maybe that was wrong. Can you point
> > > me to a dts-file with an example?
> >
> > That approach doesn't work
On Fri, 2012-08-17 at 17:14 +0200, Oleg Nesterov wrote:
> I still think that task_work_add() should synhronize with exit_task_work()
> itself and fail if necessary. But I wasn't able to convince Al ;)
I'm not at all sure how that relates to needing task_lock() in the
keyctl stuff.
Also, can't
On 08/19/2012 12:25 AM, Julia Lawall wrote:
> From: Julia Lawall
>
> The result of one call to a function is tested, and then at the second call
> to the same function, the previous result, and not the current result, is
> tested again.
>
> The semantic match that finds this problem is as
> In that case, I would recommend changing it from
>
> + /* if the pwm device exists, skip requesting the device */
> + if (drvdata->pwm)
> + return 0;
>
> to
>
> /* warn if the PWM was not released prior to reneabling it */
> WARN_ON(drvdata->pwm);
>
OK,
On 19/08/12 16:30, Marek Vasut wrote:
Dear Shawn Guo,
On 17 August 2012 10:57, Marek Vasut wrote:
Thanks ... still, is there some key for those tags? Or do you invent them
at random and then let people guess what's right? Some git grep on
Documentation directory gets me nothing.
There is
On Mon, 2012-08-20 at 06:56 +, 함명주 wrote:
> > From: anish kumar
> >
> > Instead of "const char **supported_cable" it is better to have
> > it as "const char *const *supported_cable".
> >
> > Signed-off-by: anish kumar
>
> Could you please elaborate on why it's better?
>
> (Is this fixing
On Mon, Aug 20, 2012 at 06:16:41AM +, Kim, Milo wrote:
> > > * Rather than having to do the #ifdef here, I think it would be
> > better if
> > > the PWM subsystem provided stub functions for pwm_request,
> > pwm_config,
> > > pwm_enable, pwm_disable and pwm_free that do nothing, so you can
2012/8/19 Shmulik Ladkani :
> Hi Richard,
>
> On Fri, 17 Aug 2012 16:35:22 +0200 Richard Genoud
> wrote:
>> + "MTD devices may be specified by their number, name, or
>> path to the MTD character device node.\n"
>> + "Optional \"vid_hdr_offs\" parameter
> Maybe we should get this resolved somehow in the meantime. Resolving
> the
> other issues may take another cycle or two, so you may not want to wait
> that long.
Is that job also including HAVE_PWM configurations?
Some SoCs still set HAVE_PWMs and codes exist under arch/ directory.
As I far as
Since we have already in BH context when iscsi_sw_tcp_write_space()
is called, it's unnecessary to disable BH.
Signed-off-by: Ying Xue
---
drivers/scsi/iscsi_tcp.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/scsi/iscsi_tcp.c b/drivers/scsi/iscsi_tcp.c
index
On 2012/8/17 3:33, Toshi Kani wrote:
> On Thu, 2012-08-16 at 18:28 +0800, Hanjun Guo wrote:
>> On 2012/8/13 10:54, Luck, Tony wrote:
vec = irq_to_vector(irq);
list_for_each_entry(rte, >rtes,
rte_list) {
+ if
* Andi Kleen wrote:
> This rather large patchkit enables gcc Link Time Optimization (LTO)
> support for the kernel.
>
> With LTO gcc will do whole program optimizations for
> the whole kernel and each module. This increases compile time,
> but can generate faster code.
By how much does it
On Mon, Aug 20, 2012 at 07:41:31AM +, Kim, Milo wrote:
> > Maybe we should get this resolved somehow in the meantime. Resolving
> > the
> > other issues may take another cycle or two, so you may not want to wait
> > that long.
>
> Is that job also including HAVE_PWM configurations?
> Some
On Mon, Aug 20, 2012 at 08:29:23AM +0100, Jonathan Cameron wrote:
> Mostly these prefixes are an excuse for grumpy maintainers to moan
> at people :)
Yeah, I have to become grumpy when my comment gets ignored and I have
to make it right (for several times) to avoid my upstream moaning at me.
Is
On 08/18/2012 01:37 AM, Ying Han wrote:
> On Thu, Aug 9, 2012 at 6:01 AM, Glauber Costa wrote:
>> Hi,
>>
>> This is the first part of the kernel memory controller for memcg. It has been
>> discussed many times, and I consider this stable enough to be on tree. A
>> follow
>> up to this series are
> Yes, the goal is to remove all implementations of the old framework
> (HAVE_PWM) and replace it with PWM only implementations. I suppose we
> could in the meantime add #ifdef CONFIG_HAVE_PWM around the legacy
> functions and provide dummies in the !PWM case. That might work.
Sounds great,
On 20/08/12 08:52, Shawn Guo wrote:
On Mon, Aug 20, 2012 at 08:29:23AM +0100, Jonathan Cameron wrote:
Mostly these prefixes are an excuse for grumpy maintainers to moan
at people :)
Yeah, I have to become grumpy when my comment gets ignored and I have
to make it right (for several times) to
These error paths are used more often now after deep changes to the
clock code and pinctrl is still new for imx. So help debugging and give
clues in the boot log.
Signed-off-by: Uwe Kleine-König
---
drivers/tty/serial/imx.c |3 +++
1 file changed, 3 insertions(+)
diff --git
On Fri, 17 Aug 2012, Rik van Riel wrote:
> On 08/17/2012 08:03 PM, Daniel Forrest wrote:
>
> > Based on your comments, I came up with the following patch. It boots
> > and the anon_vma/anon_vma_chain SLAB usage is stable, but I don't know
> > if I've overlooked something. I'm not a kernel
>From Charles Wang
Azat Khuzhin reported "high loadavg in linux-3.6"
After checking for upstream's code, I found Peter's patch
(Commit id:5167e8d5417bf5c322a703d2927daec727ea40dd) not be
fully applied, missing the call for calc_load_exit_idle.
After that idle exit in sampling window will always
Hello,
I'm really sorry for a late reply, but I was a bit busy with other stuff.
On Tuesday, July 31, 2012 10:17 PM Federico Vaga wrote:
> Signed-off-by: Federico Vaga
> ---
> drivers/media/video/Kconfig | 6 +-
> drivers/media/video/Makefile | 1 +
>
* Arjan van de Ven wrote:
> On 8/15/2012 8:04 AM, Peter Zijlstra wrote:
>
> > This all sounds far too complicated.. we're talking about
> > simple spreading and packing balancers without deep arch
> > knowledge and knobs, we couldn't possibly evaluate anything
> > like that.
> >
> > I was
On Tue, Aug 14, 2012 at 01:13:49PM +0200, Linus Walleij wrote:
> On Thu, Aug 9, 2012 at 5:47 PM, Lee Jones wrote:
>
> > We've done this before and it worked well last time. Here we're
> > duplicating a complex registration function to ease the process
> > of enabling it for Device Tree. As there
The count records the PAs freed, not left.
Change the debug description.
Signed-off-by: Wang Sheng-Hui
---
fs/ext4/mballoc.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
index 8eae947..f83b145 100644
--- a/fs/ext4/mballoc.c
+++
On Sun, 2012-08-19 at 11:49 -0700, Sage Weil wrote:
> I've bisected and identified this commit:
>
> netvm: propagate page->pfmemalloc to skb
>
> The skb->pfmemalloc flag gets set to true iff during the slab allocation
> of data in __alloc_skb that the the PFMEMALLOC reserves were
On Tue, Aug 14, 2012 at 10:51:02AM +0200, Linus Walleij wrote:
> On Thu, Aug 9, 2012 at 5:47 PM, Lee Jones wrote:
>
> > In the initial submission of the MSP driver msp1 and msp3's associated
> > pinctrl mechanism was passed back to platform code using a plat_init()
> > call-back routine, but it
Hi,
On 08/20/2012 09:07 AM, Sebastian Andrzej Siewior wrote:
>> I merged these changes into the patch set, and will repost it tomorrow
>> after I can test it more thoroughly.
>
> Thanks.
> While you are playing with it, I saw that you handle vbus (->pull())
> manually. This was the case in the
This patch adjusts the LPC32xx USB gadget driver to the new udc_start /
udc_stop interface.
Signed-off-by: Roland Stigge
---
Applies to v3.6-rc2
drivers/usb/gadget/lpc32xx_udc.c | 49 +++
1 file changed, 14 insertions(+), 35 deletions(-)
---
The lpc32xx_udc driver supported only one controller by defining a global
static struct for it. This patch enables multiple instances of the controller
by dynamic allocation of the struct at probe(). A static struct is kept as a
template on initialization since it does some complex preset,
This patch removes the utilization of struct usb_endpoint_descriptor, as done
by other drivers also. This was done on request by the USB gadget maintainers,
since this API is obsoleted.
Signed-off-by: Roland Stigge
---
drivers/usb/gadget/lpc32xx_udc.c | 23 +++
1 file
On Sat, Aug 11, 2012 at 2:56 PM, Sebastian Hesselbarth
wrote:
> This patch set adds a core pinctrl driver for Marvell MVEBU SoCs and
> SoC specific stubs for Armada 370, Armada XP, Dove, and Kirkwood.
> The SoC specific stubs use the pinctrl-mvebu core driver that handles
> pinctrl API and
On Mon, 2012-08-20 at 08:55 +0200, Richard Genoud wrote:
> Hi Artem,
> 2012/8/19 Artem Bityutskiy :
> > Yeah, I wanted to make it 1..256 but forgot, will do now. 0..256 would
> > need some more work to avoid division by 0.
> Division by 0 is handled in the get_bad_peb_limit() function, I don't
>
No email address provided by Azat Khuzhin, so I don't know
how to let him know this. - -!
On 08/20/2012 04:02 PM, Charles Wang wrote:
From Charles Wang
Azat Khuzhin reported "high loadavg in linux-3.6"
After checking for upstream's code, I found Peter's patch
(Commit
On 08/20/2012 10:11 AM, Roland Stigge wrote:
--- linux-2.6.orig/drivers/usb/gadget/lpc32xx_udc.c
+++ linux-2.6/drivers/usb/gadget/lpc32xx_udc.c
@@ -2608,10 +2608,9 @@ static void nop_release(struct device *d
/* nothing to free */
}
-static struct lpc32xx_udc controller = {
+static
On 08/20/2012 10:11 AM, Roland Stigge wrote:
This patch removes the utilization of struct usb_endpoint_descriptor, as done
by other drivers also. This was done on request by the USB gadget maintainers,
since this API is obsoleted.
#1 and #2 look good. #3 could use a const besides that it looks
On Mon, 2012-08-20 at 08:31 +0200, Richard Genoud wrote:
> That's right, I'll correct that in next version.
> Thanks !
I've amended this patch, added Shmulik's reviewed-by and pushed to
linux-ubi.git, thanks!
--
Best Regards,
Artem Bityutskiy
signature.asc
Description: This is a digitally
On 20/08/2012 02:01, NeilBrown wrote:
On Sun, 19 Aug 2012 18:34:28 -0500 Stan Hoeppner
wrote:
Since we are trying to set the record straight
md/RAID6 must read all devices in a RMW cycle.
md/RAID6 must read all data devices (i.e. not parity devices) which it is not
going to write to,
On Sat, Aug 18, 2012 at 07:56:31PM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> Various tables in aes_generic are accessed by assembler code.
> Mark them __visible for LTO
>
> Cc: herb...@gondor.apana.org.au
> Signed-off-by: Andi Kleen
Acked-by: Herbert Xu
--
Email: Herbert Xu
Home
On Sat, Aug 18, 2012 at 07:56:32PM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> Cc: herb...@gondor.apana.org.au
> Signed-off-by: Andi Kleen
Acked-by: Herbert Xu
--
Email: Herbert Xu
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
2012/8/20 Richard Genoud :
> 2012/8/19 Shmulik Ladkani :
>> Hi Richard,
>>
>> On Fri, 17 Aug 2012 16:35:22 +0200 Richard Genoud
>> wrote:
>>> + "MTD devices may be specified by their number, name, or
>>> path to the MTD character device node.\n"
>>> +
On Mon, 2012-08-20 at 11:25 +0300, Artem Bityutskiy wrote:
> On Mon, 2012-08-20 at 08:31 +0200, Richard Genoud wrote:
> > That's right, I'll correct that in next version.
> > Thanks !
>
> I've amended this patch, added Shmulik's reviewed-by and pushed to
> linux-ubi.git, thanks!
Sorry, actually
On Mon, Jul 9, 2012 at 10:37 PM, Jiri Olsa wrote:
> Making hardware events translations available through the sysfs.
> Adding 'events' group attribute under the sysfs x86 PMU record
> with attribute/file for each hardware event:
>
> # ls /sys/devices/cpu/events/
> branch-instructions
>
On 08/20/2012 10:19 AM, Sebastian Andrzej Siewior wrote:
> On 08/20/2012 10:11 AM, Roland Stigge wrote:
>> This patch removes the utilization of struct usb_endpoint_descriptor,
>> as done
>> by other drivers also. This was done on request by the USB gadget
>> maintainers,
>> since this API is
(CC: J. Bruce Fields)
Greg,
it looks like a fix for a regression in NFS is not mentioned in this
patch even though it was supposedly sent to -stable:
http://lkml.indiana.edu/hypermail/linux/kernel/1208.2/00594.html
I tried to locate the patch in git but could not find it anywhere. As far
as I
On Mon, 2012-08-20 at 10:06 +0200, Ingo Molnar wrote:
> > > I was really more thinking of something useful for the
> > > laptops out there, when they pull the power cord it makes
> > > sense to try and keep CPUs asleep until the one that's awake
> > > is saturated.
>
> s/CPU/core ?
I was
2012/8/20 Artem Bityutskiy :
> On Mon, 2012-08-20 at 08:55 +0200, Richard Genoud wrote:
>> Hi Artem,
>> 2012/8/19 Artem Bityutskiy :
>> > Yeah, I wanted to make it 1..256 but forgot, will do now. 0..256 would
>> > need some more work to avoid division by 0.
>> Division by 0 is handled in the
801 - 900 of 1384 matches
Mail list logo
