On Wednesday 02 January 2013 08:18 PM, Arnd Bergmann wrote:
> On Wednesday 02 January 2013, Vineet Gupta wrote:
>> On Wednesday 07 November 2012 07:43 PM, Arnd Bergmann wrote:
>>> On Wednesday 07 November 2012, Vineet Gupta wrote:
>>> +menu "ARC CPU Configuration"
>>> +
>>> +choice
>>> + prompt
On Wed, 2013-01-02 at 23:35 -0800, Dmitry Torokhov wrote:
> On Thu, Jan 03, 2013 at 04:25:09PM +1300, Tony Prisk wrote:
> > +static void __init vt8500_timer_init(void)
> > +{
> > + struct device_node *np;
> > + int timer_irq;
> > +
> > + np = of_find_matching_node(NULL, vt8500_timer_ids);
>
On Thu, Jan 03, 2013 at 04:25:09PM +1300, Tony Prisk wrote:
> +static void __init vt8500_timer_init(void)
> +{
> + struct device_node *np;
> + int timer_irq;
> +
> + np = of_find_matching_node(NULL, vt8500_timer_ids);
> + if (!np) {
> + pr_err("%s: Timer description
On Wed, Jan 02, 2013 at 11:04:24AM -0800, Dan Magenheimer wrote:
> > From: Dave Hansen [mailto:d...@linux.vnet.ibm.com]
> > Subject: Re: [PATCH 7/8] zswap: add to mm/
>
> Hi Dave --
>
> I suspect we are in violent agreement but just to make sure...
>
> Although zswap is the current example, I
Hi Stephen,
On Thu, 3 Jan 2013 12:06:50 +1100
Stephen Rothwell wrote:
> Today's linux-next merge of the kvm tree got conflicts in
> arch/s390/include/asm/irq.h and arch/s390/kernel/irq.c between commit
> bfb048f594d5 ("s390/irq: remove split irq fields from /proc/stat") from
> the s390 tree and
Tegra USB host driver is using port instance number,
to handle some of the hardware issues on SOC e.g. reset PORT0
twice etc. As instance number based handling looks ugly,
making use of information passed through DT for achieving this.
Signed-off-by: Venu Byravarasu
Acked-by: Alan Stern
---
As Tegra USB host driver is using instance number for resetting
PORT0 twice, adding a new DT property for handling this.
Signed-off-by: Venu Byravarasu
---
.../bindings/usb/nvidia,tegra20-ehci.txt |2 ++
arch/arm/boot/dts/tegra20.dtsi |1 +
2 files changed,
Tegra USB host driver is using port instance number,
to handle some of the hardware issues on SOC e.g. reset PORT0
twice etc. As instance number based handling looks ugly,
added a new property to USB DT node for this purpose.
Modified host driver to make use of the information passed
through DT to
Hi,
On Sunday 30 December 2012 02:13 AM, ahema...@gmail.com wrote:
From: ahemaily
The variable dma_lch_count used for comparison (omap_dma_reserve_channels <=
dma_lch_count)
before it initialized to the value from omap_dma_dev_attr : d->lch_count.
I change the place of dma_lch_count
On Wed, Jan 02, 2013 at 06:10:13PM -0800, Bryan Wu wrote:
> Hi Peter,
>
> I merged this patchset into my for-next branch already.
>
> Thanks for pushing this.
Hi Bryan,
Did you also take the PWM patches (3-5)? I was going to add those to my
tree, but if you already take them feel free to add
Marc MERLIN writes:
> I had pretty repeated crashes when plugging power back into my running
> laptop, but the display just freezes and I can't get a dump.
> For the crash here, I did: suspend to RAM, plug power back in, wake up.
> Laptop crashed about 3 seconds after wakeup.
Sounds like
PARISC defines /proc/sys/kernel/unaligned-trap to runtime toggle
unaligned access emulation.
The exact mechanics of enablig/disabling are still arch specific, we can
make the sysctl usable by other arches.
Signed-off-by: Vineet Gupta
Cc: "James E.J. Bottomley"
Cc: Helge Deller
Cc: "Eric W.
Hi,
This came out ARC Port's review by Arnd where he suggested using the existing
sysctl knobs in parisc and/or ia64 for runtime controlling unaligned access
emulation.
Turns out that ARC port needs bit of both.
The common sysctl knobs are now #ifdef based on init/Kconfig options which
the
Hi,
This came out ARC Port's review by Arnd where he suggested using the existing
sysctl knobs in parisc and/or ia64 for runtime controlling unaligned access
emulation.
Turns out that ARC port needs bit of both.
The common sysctl knobs are now #ifdef based on init/Kconfig options which
the
IA64 defines /proc/sys/kernel/ignore-unaligned-usertrap to control
verbosw warnings on unaligned access emaultion.
While the exact menchaincs (ignore/shout) are still arch specific, we
can make the sysctl usable by other arches.
Signed-off-by: Vineet Gupta
Cc: Tony Luck
Cc: Fenghua Yu
Cc:
Stephen Warren wrote @ Wed, 2 Jan 2013 20:02:53 +0100:
> On 12/16/2012 11:18 PM, Hiroshi Doyu wrote:
> > Set Snoop Control Unit(SCU) register base address dynamically from DT.
>
> Hiroshi, what's the status on this patch series? I think Rob had
> comments/objections on patch 4; are you going to
Use 'platform_device' rather than i2c client device node.
Argument is added in lp8788_config_ldo_enable_mode().
Signed-off-by: Milo(Woogyom) Kim
---
drivers/regulator/lp8788-ldo.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git
The lp8788-ldo is a platform driver of lp8788-mfd.
The platform device is allocated when mfd_add_devices() is called
in lp8788-mfd.
On the other hand, 'lp->dev' is the i2c client device.
Therefore, this 'platform_device' is a proper parent device in case of
resource managed mem alloc,
Remove space before semicolon in for-loop.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/regulator/lp8788-buck.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/lp8788-buck.c b/drivers/regulator/lp8788-buck.c
index 98770e8..1161949 100644
---
Use 'platform_device' rather than i2c client device node.
Arguments are added in lp8788_init_dvs() and lp8788_dvs_gpio_request().
Signed-off-by: Milo(Woogyom) Kim
---
drivers/regulator/lp8788-buck.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git
The lp8788-buck is a platform driver of lp8788-mfd.
The platform device is allocated when mfd_add_devices() is called
in lp8788-mfd.
On the other hand, 'lp->dev' is the i2c client device.
Therefore, this 'platform_device' is a proper parent device in case of
resource managed mem alloc,
The lp8788-charger is a platform driver of lp8788-mfd.
The platform device is allocated when mfd_add_devices() is called
in lp8788-mfd.
On the other hand, 'lp->dev' is the i2c client device.
Therefore, this 'platform_device' is a proper parent device in case of
resource managed mem alloc
Use 'platform_device' in kernel messages rather than i2c client
device node.
lp8788_update_charger_params() needs additional argument, 'pdev'.
Then, remove unnecessary lp8788 private data in lp8788_irq_register().
Signed-off-by: Milo(Woogyom) Kim
---
drivers/power/lp8788-charger.c | 12
Use 'dev' of iio device in a kernel message rather than i2c client device node.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/iio/adc/lp8788_adc.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iio/adc/lp8788_adc.c b/drivers/iio/adc/lp8788_adc.c
index
The lp8788-adc is a platform driver of lp8788-mfd.
The platform device is allocated when mfd_add_devices() is called
in lp8788-mfd.
On the other hand, 'lp->dev' is the i2c client device.
Therefore, this 'platform_device' is a proper parent device of
iio device and device kernel message.
The lp8788-keyled is a platform driver of lp8788-mfd.
The platform device is allocated when mfd_add_devices() is called
in lp8788-mfd.
On the other hand, 'lp->dev' is the i2c client device.
Therefore, this 'platform_device' is a proper parent device in case of
resource managed mem alloc,
On 12/20/2012 07:49 PM, Michel Lespinasse wrote:
The vm_populate() code populates user mappings without constantly
holding the mmap_sem. This makes it susceptible to racy userspace
programs: the user mappings may change while vm_populate() is running,
and in this case vm_populate() may end up
On 12/22/2012 04:45 AM, Michel Lespinasse wrote:
do_mmap_pgoff() rounds up the desired size to the next PAGE_SIZE multiple,
however there was no equivalent code in mm_populate(), which caused issues.
This could be fixed by introduced the same rounding in mm_populate(),
however I think it's
On Thursday 03 January 2013 05:20 AM, Andrew Morton wrote:
On Thu, 27 Dec 2012 20:29:14 +0530
Laxman Dewangan wrote:
On Thursday 27 December 2012 08:26 PM, Marc Dietrich wrote:
Hi Laxman,
On Friday 21 December 2012 20:42:28 you wrote:
+
+ /* Set epoch start as 00:00:00:01:01:2000 */
On Thu, 2013-01-03 at 17:13 +1100, Benjamin Herrenschmidt wrote:
> Hi Linus !
>
> Here are a couple of small powerpc fixes. They aren't new bugs (and
> they are both CCed to stable) but I didn't see the point of sitting
> on the fixes any longer.
Looks like I still need to fix my script to get
Hi Linus !
Here are a couple of small powerpc fixes. They aren't new bugs (and
they are both CCed to stable) but I didn't see the point of sitting
on the fixes any longer.
Oh and happy new year !
Cheers,
Ben.
The following changes since commit d1c3ed669a2d452cacfb48c2d171a1f364dae2ed:
Linux
On Thursday 03 January 2013 03:30 AM, Stephen Warren wrote:
On 12/27/2012 07:47 AM, Prashant Gaikwad wrote:
APB misc contains multiple registers required by different modules
such as CAR.
I don't see a DT binding document that describes what
nvidia,tegra30-apbmisc means. Also, the register
On 21.12.2012 15:50, Lucas Stach wrote:
> Am Freitag, den 21.12.2012, 13:39 +0200 schrieb Terje Bergstrom:
>> Some of the issues left open:
>> * Register definitions still use static inline. There has been a
>>debate about code style versus ability to use compiler type
>>checking and code
On 01/03/2013 01:50 PM, Terje Bergström wrote:
> On 03.01.2013 05:31, Mark Zhang wrote:
>> Sorry I didn't get it. Yes, in current design, you can pin all mem
>> handles in one time but I haven't found anything related with "locking
>> only once per submit".
>>
>> My idea is:
>> - remove
On 12/20/2012 07:49 PM, Michel Lespinasse wrote:
In find_extend_vma(), we don't need mlock_vma_pages_range() to verify the
vma type - we know we're working with a stack. So, we can call directly
into __mlock_vma_pages_range(), and remove the last make_pages_present()
call site.
Note that we
On 12/20/2012 07:49 PM, Michel Lespinasse wrote:
After the MAP_POPULATE handling has been moved to mmap_region() call sites,
the only remaining use of the flags argument is to pass the MAP_NORESERVE
flag. This can be just as easily handled by do_mmap_pgoff(), so do that
and remove the
On 12/20/2012 07:49 PM, Michel Lespinasse wrote:
Signed-off-by: Michel Lespinasse
Changelog?
Acked-by: Rik van Riel
--
All rights reversed
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On 03.01.2013 05:31, Mark Zhang wrote:
> Sorry I didn't get it. Yes, in current design, you can pin all mem
> handles in one time but I haven't found anything related with "locking
> only once per submit".
>
> My idea is:
> - remove "job->addr_phys"
> - assign "job->reloc_addr_phys" &
Many spinlocks are embedded in data structures; having many CPUs
pounce on the cache line the lock is in will slow down the lock
holder, and can cause system performance to fall off a cliff.
The paper "Non-scalable locks are dangerous" is a good reference:
Many spinlocks are embedded in data structures; having many CPUs
pounce on the cache line the lock is in will slow down the lock
holder, and can cause system performance to fall off a cliff.
The paper "Non-scalable locks are dangerous" is a good reference:
Simple fixed value proportional backoff for ticket spinlocks.
By pounding on the cacheline with the spin lock less often,
bus traffic is reduced. In cases of a data structure with
embedded spinlock, the lock holder has a better chance of
making progress.
If we are next in line behind the current
Moving the wait loop for congested loops to its own function allows
us to add things to that wait loop, without growing the size of the
kernel text appreciably.
Signed-off-by: Rik van Riel
Reviewed-by: Steven Rostedt
Reviewed-by: Michel Lespinasse
Reviewed-by: Rafael Aquini
---
v2: clean up
From: Eric Dumazet
This code prints out the maximum spinlock delay value and the
backtrace that pushed it that far.
On systems with serial consoles, the act of printing can cause
the spinlock delay value to explode. It can still be useful as
a debugging tool, but is probably too verbose to
From: Eric Dumazet
Eric Dumazet found a regression with the spinlock backoff code,
in workloads where multiple spinlocks were contended, each having
a different wait time.
This patch has multiple delay values per cpu, indexed on a hash
of the lock address, to avoid that problem.
Eric Dumazet
Hi Joerg,
It's been a while since I submitted this patch. I have tried to address your
comments regarding the subwindow attribute. I would really appreciate if I can
get some feedback on this patch.
Regards
Varun
> -Original Message-
> From: Sethi Varun-B16395
> Sent: Friday, December
On Tue, 1 Jan 2013, Simon Jeons wrote:
>
> Hi Petr and Hugh,
>
> One offline question, thanks for your clarify.
Perhaps not as offline as you intended :)
>
> How to understand age = (unsigned char)(ksm_scan.seqnr -
> rmap_item->address);? It used for what?
As you can see,
On 01/02/2013 09:25 PM, Tony Prisk wrote:
> Move mach-vt8500/irq.c to drivers/irqchip/irq-vt8500.c and make
> necessary Makefile changes. No code changes required.
>
> Signed-off-by: Tony Prisk
> ---
> CC: Thomas Gleixner
> arch/arm/mach-vt8500/Makefile |2 +-
>
On Wed, 2013-01-02 at 22:38 -0600, Rob Herring wrote:
> > CC: Thomas Gleixner
> > arch/arm/mach-vt8500/Makefile |2 +-
> > arch/arm/mach-vt8500/common.h |7 +-
> > arch/arm/mach-vt8500/irq.c| 253
> > -
> > drivers/irqchip/Makefile |
2013/1/2, Jan Kara :
> On Tue 01-01-13 08:51:04, Wanpeng Li wrote:
>> On Mon, Dec 31, 2012 at 12:30:54PM +0100, Jan Kara wrote:
>> >On Sun 30-12-12 14:59:50, Namjae Jeon wrote:
>> >> From: Namjae Jeon
>> >>
>> >> Consider Process A: huge I/O on sda
>> >> doing heavy write operation -
VOLATILE imply the the pages in the range isn't working set any more
so it's pointless that make them to THP/KSM.
Cc: Rik van Riel
Cc: Hugh Dickins
Cc: Andrea Arcangeli
Signed-off-by: Minchan Kim
---
mm/huge_memory.c |9 +++--
mm/ksm.c |3 ++-
2 files changed, 9
This patch adds new system call m[no]volatile.
If someone asks is_volatile system call, it could be added, too.
The reason why I introduced new system call instead of madvise is
m[no]volatile vma handling is totally different with madvise's vma
handling.
1) The m[no]volatile should be successful
VM don't need to swap out volatile pages. Instead, it just discards
pages and set true to the vma's purge state so if user try to access
purged vma without calling mnovolatile, it will encounter SIGBUS.
Cc: Rik van Riel
Cc: Mel Gorman
Cc: Hugh Dickins
Signed-off-by: Minchan Kim
---
This patch add pgvolatile vmstat so admin can see how many of volatile
pages are discarded by VM until now.
Signed-off-by: Minchan Kim
---
include/linux/vm_event_item.h |3 +++
mm/mvolatile.c|1 +
mm/vmstat.c |3 +++
3 files changed, 7 insertions(+)
Now kswapd can discard volatile pages so let's cover it for vmstat.
Signed-off-by: Minchan Kim
---
include/linux/vm_event_item.h |3 ++-
mm/mvolatile.c|5 -
mm/vmstat.c |3 ++-
3 files changed, 8 insertions(+), 3 deletions(-)
diff --git
This patch adds volatile page discard hook to kswapd for
minimizing eviction of working set and enable discarding
volatile page although we don't turn on swap.
This patch is copied heavily from THP.
Cc: Hugh Dickins
Cc: Andrea Arcangeli
Cc: Rik van Riel
Cc: Mel Gorman
Signed-off-by: Minchan
This is still RFC because we need more input from user-space
people, more stress test, design discussion about interface/reclaim
policy of volatile pages and I want to expand this concept to tmpfs
volatile range if it is possbile without big performance drop of
anonymous volatile range.
(Let's
If we found a page is in VOLATILE vma, hurry up discarding
instead of access bit check because it's very unlikey working set.
Next patch will use it.
Cc: Rik van Riel
Cc: Mel Gorman
Signed-off-by: Minchan Kim
---
mm/rmap.c |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff
Add page_locked parameter for avoiding trylock_page.
Next patch will use it.
Cc: Hugh Dickins
Cc: Mel Gorman
Cc: Rik van Riel
Signed-off-by: Minchan Kim
---
include/linux/swap.h |6 +++---
mm/fremap.c |2 +-
mm/memory.c |2 +-
mm/shmem.c |2 +-
Hi all,
Changes since 20130102:
The net-next tree gained a build failure for which I applied a patch.
The kvm tree gained a conflict against the s390 tree.
The pinctrl tree gained a conflict against the driver-core.current tree
It's a new year, people are getting back to work, and trying
desperately to forget the over-eating that has been going on for the
last two weeks. And hey, to celebrate, here's -rc2!
The patch is fairly small, and largely dominated by the GPU updates
and the trivial removal of __devinit/exit in
On 3 January 2013 06:43, Rafael J. Wysocki wrote:
>> BTW, i consider them as fixes and so would make sense to get them in next rc.
>> What do you think?
>
> Yes, if somebody tells me "yes, this fixes a problem for me". Otherwise,
> I don't quite see the reason.
I don't know how much people test
On 01/02/2013 05:42 PM, Terje Bergström wrote:
> On 28.12.2012 11:14, Mark Zhang wrote:
>> diff --git a/drivers/gpu/drm/tegra/gr2d.c b/drivers/gpu/drm/tegra/gr2d.c
>> index a936902..c3ded60 100644
>> --- a/drivers/gpu/drm/tegra/gr2d.c
>> +++ b/drivers/gpu/drm/tegra/gr2d.c
>> @@ -131,6 +131,14 @@
From: Stephen Rothwell
Date: Thu, 3 Jan 2013 14:23:53 +1100
> Caused by commit 13159183ec7a ("qlcnic: 83xx base driver") from the
> net-next tree. Why is this commit adding a function that already exists
> globally?
And this is after I pushed back on this patch series 5 times or so.
You
Move mach-vt8500/irq.c to drivers/irqchip/irq-vt8500.c and make
necessary Makefile changes. No code changes required.
Signed-off-by: Tony Prisk
---
CC: Thomas Gleixner
arch/arm/mach-vt8500/Makefile |2 +-
arch/arm/mach-vt8500/common.h |7 +-
arch/arm/mach-vt8500/irq.c| 253
These two patches move the irq and clocksource code out of mach-vt8500
and into drivers/irqchip and drivers/clocksource respectively.
Because they affect the same files in mach-vt8500 I thought it may be
easier if it goes through arm-soc, but I note Thomas is the maintainer for
both irqchip and
Move mach-vt8500/timer.c to drivers/clocksource/vt8500_timer.c
and make necessary changes to Kconfig and Makefile.
vt8500_timer is moved from vt8500.c to clocksource/vt8500_timer.c
and added to common.h for reference from the board descriptor.
Signed-off-by: Tony Prisk
---
CC: John Stultz
CC:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/net/built-in.o: In function `pci_get_domain_bus_and_slot':
(.opd+0x449e8): multiple definition of `pci_get_domain_bus_and_slot'
drivers/pci/built-in.o:(.opd+0x1c98): first defined here
On Wed, Jan 02, 2013 at 07:49:23PM -0500, Steven Rostedt wrote:
> On Wed, 2013-01-02 at 13:29 -0800, Paul E. McKenney wrote:
> > On Wed, Jan 02, 2013 at 03:56:30PM -0500, Steven Rostedt wrote:
> > > On Wed, Jan 02, 2013 at 08:09:20PM +0100, Ralf Hildebrandt wrote:
> > > > This happened of a
On 12/20/2012 07:49 PM, Michel Lespinasse wrote:
Signed-off-by: Michel Lespinasse
Acked-by: Rik van Riel
--
All rights reversed
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On 01/02/2013 05:25 PM, Terje Bergström wrote:
> On 26.12.2012 11:42, Mark Zhang wrote:
[...]
>
>>
>> if (!de)
>> diff --git a/drivers/gpu/host1x/dev.c b/drivers/gpu/host1x/dev.c
>> index 07e8813..01ed10d 100644
>> --- a/drivers/gpu/host1x/dev.c
>> +++ b/drivers/gpu/host1x/dev.c
>> @@
Thanks. It is not too late to review this code. But I'd prefer not to
address refactoring issues with this patch, which is supposed to fix a
deadlock with some drivers. So I'd rather not to add function
renaming, suppressions, etc. that have an effect outside cpu_rmap's
code. Instead, I'd like to
On Thu, Jan 03, 2013 at 02:35:59AM +0100, Pablo Neira Ayuso wrote:
> > when NF_CONNTRACK is not enabled (build was on i386):
> >
> > CC [M] net/netfilter/xt_CT.o
> > In file included from net/netfilter/xt_CT.c:16:0:
> > include/net/netfilter/nf_conntrack.h:77:22: error: field 'ct_general' has
Hello, Rusty.
On Thu, Jan 03, 2013 at 11:17:11AM +1030, Rusty Russell wrote:
> > So, I guess this currently is caught in a place which isn't here or
> > there. I'm pretty skeptical whether it makes sense to bother about
> > static usages tho. Can I keep them for static ones?
>
> I didn't
On 12/20/2012 07:49 PM, Michel Lespinasse wrote:
Signed-off-by: Michel Lespinasse
Changelog could use some help :)
Other than that:
Reviewed-by: Rik van Riel
--
All rights reversed
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On 12/20/2012 07:49 PM, Michel Lespinasse wrote:
When creating new mappings using the MAP_POPULATE / MAP_LOCKED flags
(or with MCL_FUTURE in effect), we want to populate the pages within the
newly created vmas. This may take a while as we may have to read pages
from disk, so ideally we want to
Hi Peter,
I merged this patchset into my for-next branch already.
Thanks for pushing this.
-Bryan
On Fri, Dec 21, 2012 at 1:43 AM, Peter Ujfalusi wrote:
> Hello,
>
> Changes since v4:
> - Commit message for patch #7 (DT binding for the leds-pwm driver) has been
> updated
>
> Changes since
Hi Linus:
Please consider the following changes since commit
a49f0d1ea3ec94fc7cf33a7c36a16343b74bd565:
Linux 3.8-rc1 (2012-12-21 17:19:00 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/cooloney/linux-leds.git
for you to fetch changes up to
Sorry, I signed off with wrong email address. Please ignore this pull
request email.
I will resent one.
-Bryan
On Wed, Jan 2, 2013 at 5:50 PM, Bryan Wu wrote:
> Hi Linus:
>
> Please consider the following changes since commit
> a49f0d1ea3ec94fc7cf33a7c36a16343b74bd565:
>
> Linux 3.8-rc1
Hi Linus:
Please consider the following changes since commit
a49f0d1ea3ec94fc7cf33a7c36a16343b74bd565:
Linux 3.8-rc1 (2012-12-21 17:19:00 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/cooloney/linux-leds.git
fixes-for-3.8
for you to fetch
From: Rafael J. Wysocki
At one point acpi_device_set_id() checks if acpi_device_hid(device)
returns NULL, but that never happens, so system bus devices with an
empty list of PNP IDs are given the dummy HID ("device") instead of
the "system bus HID" ("LNXSYBUS"). Fix the code to use the right
Hi,
On Wed, Jan 02, 2013 at 10:39:43AM -0800, Randy Dunlap wrote:
> On 01/01/13 20:12, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20121224:
> >
>
> when NF_CONNTRACK is not enabled (build was on i386):
>
> CC [M] net/netfilter/xt_CT.o
> In file included from
Hi Linus,
Today's linux-next merge of the pinctrl tree got a conflict in
drivers/pinctrl/pinctrl-nomadik.c between commit c2c57b329c7b ("Drivers:
pinctrl: remove __dev* attributes") from the driver-core.current tree and
commit f7ae849b80de ("pinctrl/nomadik: adopt pinctrl sleep mode
management")
Sasha Levin writes:
> If we try to finit_module on a file sized 0 bytes vmalloc will
> scream and spit out a warning.
>
> Since modules have to be bigger than 0 bytes anyways we can just
> check that beforehand and avoid the warning.
Applied, but I added the comment you somehow missed :)
Jonathan Kliegman writes:
> The section mismatch warning can be easy to miss during the kernel build
> process. Allow it to be marked as fatal to be easily caught and prevent
> bugs from slipping in.
>
> Signed-off-by: Jonathan Kliegman
Hmm, a CONFIG option with no Kconfig entry? That seems
Tejun Heo writes:
> Hello, Rusty.
>
> On Wed, Jan 02, 2013 at 03:12:15PM +1030, Rusty Russell wrote:
>> > Hmmm? cpumask_t can't be used for stack but other than that I don't
>> > see how it would be deprecated completely. Rusty, can you please
>> > chime in?
>>
>> The
Michael Kerrisk writes:
> Hi Rusty,
Hi Michael,
> The description here is rather thin. Could you supply a sentence or
> two for each of MODULE_INIT_IGNORE_MODVERSIONS and
> MODULE_INIT_IGNORE_VERMAGIC that would be suitable for the manual
> page?
>
> Thanks,
There are one or two safety checks
On Wednesday, January 02, 2013 11:59:57 AM Viresh Kumar wrote:
> On 16 December 2012 19:07, Viresh Kumar wrote:
> > On 16 December 2012 18:34, Rafael J. Wysocki wrote:
>
> >> Well, this series makes sense to me, but I'd like to hear what the other
> >> people
> >> think.
> >
> > That sounds
Hi all,
Today's linux-next merge of the kvm tree got conflicts in
arch/s390/include/asm/irq.h and arch/s390/kernel/irq.c between commit
bfb048f594d5 ("s390/irq: remove split irq fields from /proc/stat") from
the s390 tree and commit 7e64e0597fd6 ("KVM: s390: Add a channel I/O
based virtio
On Wed, Jan 2, 2013 at 4:59 PM, Alex Deucher wrote:
>>>
>>
>> Catching up with this thread. I reverted the
>>
>> drm/radeon: use async dma for ttm buffer moves on 6xx-SI
>> commit id: 2d6cc7296d4ee128ab0fa3b715f0afde511f49c2
>>
>> Do I need to apply this patch without reverting
>>
On 01/03/2013 01:59 AM, Alex Deucher wrote:
On Wed, Jan 2, 2013 at 6:58 PM, Shuah Khan wrote:
On Wed, Jan 2, 2013 at 4:37 PM, Alex Deucher wrote:
On Wed, Jan 2, 2013 at 5:38 PM, Markus Trippelsdorf
wrote:
On 2013.01.02 at 17:31 -0500, Jerome Glisse wrote:
Please affected people can you
On Wed, 2013-01-02 at 13:29 -0800, Paul E. McKenney wrote:
> On Wed, Jan 02, 2013 at 03:56:30PM -0500, Steven Rostedt wrote:
> > On Wed, Jan 02, 2013 at 08:09:20PM +0100, Ralf Hildebrandt wrote:
> > > This happened of a virtual guest (Linux mail 3.2.0-35-virtual #55-Ubuntu
> > > SMP Wed Dec 5
From: Jovi Zhang
Without this patch, we can register a uprobe event for a directory.
Enabling such a uprobe event would fail anyway .
Example:
$ echo 'p /bin:0x4245c0' > /sys/kernel/debug/tracing/uprobe_events
However dirctories cannot be valid targets for uprobe.
Hence verify if the target is
From: Steven Rostedt
Sparse complains when is_signed_type() is used on a pointer.
This macro is needed for the format output used for ftrace
and perf, to know if a binary field is a signed type or not.
The is_signed_type() macro is used against all fields that are
recorded by events to automate
Ingo,
As it's still an early -rc, it would be good to get these fixes into
mainline before the next release.
Thanks,
-- Steve
Please pull the latest tip/perf/urgent tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
tip/perf/urgent
Head
From: Steven Rostedt
If some other kernel subsystem has a module notifier, and adds a kprobe
to a ftrace mcount point (now that kprobes work on ftrace points),
when the ftrace notifier runs it will fail and disable ftrace, as well
as kprobes that are attached to ftrace points.
Here's the error:
On Wed, 2013-01-02 at 18:34 -0600, Bjorn Helgaas wrote:
> On Wed, Jan 2, 2013 at 6:06 PM, Joe Perches wrote:
> > Add YA check to printk style.
> >
> > dev_ uses are functions and generate smaller
> > object code than dev_printk(KERN_.
[]
> > diff --git a/scripts/checkpatch.pl
On Mon, Dec 24, 2012 at 06:11:45PM +0800, ycn...@gmail.com wrote:
> From: Yanchuan Nian
>
> In the procedure of CREATE_SESSION, the state is locked after
> alloc_conn_from_crses(). If the allocation fails, the function
> goes to "out_free_session", and then "out" where there is an
> unlock
On Wednesday, January 02, 2013 04:07:32 PM Bjorn Helgaas wrote:
> On Thu, Dec 27, 2012 at 10:32:13PM +0100, Rafael J. Wysocki wrote:
> > To that end, split pci_create_root_bus() into two functions,
> > pci_alloc_root() and pci_add_root(), that will allocate memory for
> > the new PCI bus and
On Wed, Jan 2, 2013 at 6:06 PM, Joe Perches wrote:
> Add YA check to printk style.
>
> dev_ uses are functions and generate smaller
> object code than dev_printk(KERN_.
>
> Signed-off-by: Joe Perches
> ---
> scripts/checkpatch.pl | 10 ++
> 1 file changed, 10 insertions(+)
>
> diff
On Mon, Dec 24, 2012 at 06:11:27PM +0800, ycn...@gmail.com wrote:
> From: Yanchuan Nian
>
> In alloc_session(), numslots is the correct slot number used by the session.
> But the slot number passed to nfsd4_put_drc_mem() is the one from nfs client.
Thanks, applying for 3.9.--b.
>
>
1 - 100 of 748 matches
Mail list logo
