On 02/10/2012 02:01, Borislav Petkov wrote:
On Tue, Oct 02, 2012 at 12:12:31AM +0800, Daniel J Blueman wrote:
On 01/10/2012 18:06, Borislav Petkov wrote:
On Mon, Oct 01, 2012 at 02:42:05PM +0800, Daniel J Blueman wrote:
When booting on a federated multi-server system, the processor Northbridge
On 10/03/2012 02:06 AM, David Miller wrote:
From: Jeff Garzik
Date: Wed, 3 Oct 2012 01:45:42 -0400
1) tcrypt setup blatantly wrong. What is the best setup here? Define a
separate entry for each digest length? Is there some special string
descriptor format that is desired, like "sha3-256" or
devm_kfree and devm_iounmap should not have to be explicitly used
Signed-off-by: Kuninori Morimoto
---
This patch is based on Devendra's
[PATCH] thermal: solve compilation errors in rcar_thermal
drivers/thermal/rcar_thermal.c | 18 ++
1 file changed, 2 insertions(+), 16 deleti
On Tue, 2012-10-02 at 14:14 +0100, Mel Gorman wrote:
> On Tue, Oct 02, 2012 at 11:31:22AM +0200, Mike Galbraith wrote:
> > On Tue, 2012-10-02 at 09:45 +0100, Mel Gorman wrote:
> > > On Tue, Oct 02, 2012 at 09:49:36AM +0200, Mike Galbraith wrote:
> >
> > > > Hm, 518cd623 fixed up the troubles I s
Hi Samuel,
Hi On Mon, Oct 01, 2012 at 04:52:02, Samuel Ortiz wrote:
> Hi Jonathan,
>
> On Sat, Sep 29, 2012 at 10:50:19AM +0100, Jonathan Cameron wrote:
> > On 09/26/2012 11:09 AM, Patil, Rachna wrote:
> > > Hi Shubhrajyoti,
> > >
> > > On Wed, Sep 26, 2012 at 12:10:51, Datta, Shubhrajyoti wrote
On Fri, 28 Sep 2012, Josh Triplett wrote:
> That issue doesn't relate to __flatten, though; it only relates to
> __weak. Since __flatten (and __compiletime_object_size) will work fine
> on 4.1.0 and 4.1.1, don't exclude them just because the definition for
> __weak elsewhere in the file excludes
Hi Stephen,
On Wed, Oct 3, 2012 at 8:29 AM, Stephen Rothwell wrote:
> Well, here we are at another merge window and the kvmtool tree is still
> not merged. So, is it likely that it will be merged in this merge
> window? or the next? If not, can I please remove it from linux-next
> (and have it
Hi Hans,
On Wed, Oct 3, 2012 at 12:10 PM, Hans Verkuil wrote:
> On Wed October 3 2012 08:27:38 Prabhakar wrote:
>> From: Lad, Prabhakar
>>
>> recent patch with commit id 4f996594ceaf6c3f9bc42b40c40b0f7f87b79c86
>> which makes vidioc_s_crop const, was causing a following build warning,
>>
>> vpbe
On Fri, 28 Sep 2012, Daniel Santos wrote:
> Signed-off-by: Daniel Santos
After this is folded into the previous patch in the series,
"compiler{,-gcc4}.h: Remove duplicate macros", then:
Acked-by: David Rientjes
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Wed October 3 2012 08:27:38 Prabhakar wrote:
> From: Lad, Prabhakar
>
> recent patch with commit id 4f996594ceaf6c3f9bc42b40c40b0f7f87b79c86
> which makes vidioc_s_crop const, was causing a following build warning,
>
> vpbe_display.c: In function 'vpbe_display_s_crop':
> vpbe_display.c:640: w
On Fri, 28 Sep 2012, Josh Triplett wrote:
> GCC 4.1.0 and 4.1.1 miscompiling __weak has nothing to do with
> __compiletime_object_size; why should *this* version check exclude those
> versions?
>
Agreed, we shouldn't be relying on any #error directives to fail the build
and then try to factor t
On 10/02/12 18:36, Arnd Bergmann wrote:
> The symbol "GPIO24_SSP1_SFRM" is defined in both mfp-pxa27x.h and
> mfp-pxa25x.h. Since the macro is not actually used in the cm-x2xx.c
> file, but it includes both headers, a safe workaround should be
> to just undefine it from the .c file. This is a bit h
On Mon October 1 2012 14:52:48 Prabhakar wrote:
> From: Lad, Prabhakar
>
> recent patch with commit id 4f996594ceaf6c3f9bc42b40c40b0f7f87b79c86
> which makes vidioc_s_crop const, was causing a following build error.
>
> vpfe_capture.c: In function 'vpfe_s_crop':
> vpfe_capture.c:1695: error: ass
From: Lad, Prabhakar
while testing display on dm644x, for ED out-range signals
was observed. This patch fixes appropriate clock setting
for ED.
Signed-off-by: Lad, Prabhakar
Signed-off-by: Manjunath Hadli
Cc: Sekhar Nori
---
arch/arm/mach-davinci/dm644x.c |3 +--
1 files changed, 1 inser
From: Lad, Prabhakar
This patch replaces V4L2_OUT_CAP_CUSTOM_TIMINGS macro with
V4L2_OUT_CAP_DV_TIMINGS. As V4L2_OUT_CAP_CUSTOM_TIMINGS is being phased
out.
Signed-off-by: Lad, Prabhakar
Signed-off-by: Manjunath Hadli
Cc: Sekhar Nori
Cc: Hans Verkuil
Cc: Mauro Carvalho Chehab
---
arch/arm/
On Fri, 28 Sep 2012, Daniel Santos wrote:
> Throughout compiler*.h, many version checks are made. These can be
> simplified by using the macro that gcc's documentation recommends.
> However, my primary reason for adding this is that I need bug-check
> macros that are enabled at certain gcc versio
On Fri, 28 Sep 2012, Daniel Santos wrote:
> This helps to keep the file from getting confusing, removes one
> duplicate version check and should encourage future editors to put new
> macros where they belong.
>
> Signed-off-by: Daniel Santos
Acked-by: David Rientjes
--
To unsubscribe from this
From: Lad, Prabhakar
recent patch with commit id 4f996594ceaf6c3f9bc42b40c40b0f7f87b79c86
which makes vidioc_s_crop const, was causing a following build warning,
vpbe_display.c: In function 'vpbe_display_s_crop':
vpbe_display.c:640: warning: initialization discards qualifiers from pointer
targe
On Fri, 28 Sep 2012, Daniel Santos wrote:
> NOTE: this is has already been comitted to -mm
>
> __attribute__((error(msg))) was introduced in gcc 4.3 (not 4.4) and as I
> was unable to find any gcc bugs pertaining to it, I'm presuming that it
> has functioned as advertised since 4.3.0.
>
> Signed
Some quick fixes after today's merge-window pull.
1) Add missing dependency on Sparc DES driver, oops.
From Dave Jones.
2) Tell GCC that prom_printf() is printf-like and fix the few
resultiing warnings. From Akinobu Mita.
3) Niagara-2 memcpy doesn't provide it's return value correctly
On 10/03/2012 09:20 AM, Srivatsa S. Bhat wrote:
> On 10/03/2012 06:15 AM, Jiri Kosina wrote:
>> On Tue, 2 Oct 2012, Paul E. McKenney wrote:
>>
>>> On Wed, Oct 03, 2012 at 01:48:21AM +0200, Jiri Kosina wrote:
On Tue, 2 Oct 2012, Paul E. McKenney wrote:
> Indeed. Slab seems to be doing
From: Jeff Garzik
Date: Wed, 3 Oct 2012 01:45:42 -0400
> 1) tcrypt setup blatantly wrong. What is the best setup here? Define a
> separate entry for each digest length? Is there some special string
> descriptor format that is desired, like "sha3-256" or "sha3(256)"?
Good question. The base n
On Fri, Sep 14, 2012 at 7:11 PM, benjamin.tissoires
wrote:
> From: Benjamin Tissoires
>
> Microsoft published the protocol specification of HID over i2c:
> http://msdn.microsoft.com/en-us/library/windows/hardware/hh852380.aspx
>
> This patch introduces an implementation of this protocol.
>
> This
Hi Dmitry,
On Tue, Oct 2, 2012 at 11:48 AM, Dmitry Torokhov
wrote:
> Hi Sourav,
>
> On Mon, Oct 01, 2012 at 04:31:50PM +0530, Sourav Poddar wrote:
>> From: G, Manjunath Kondaiah
>>
>> SMSC ECE1099 is a keyboard scan or GPIO expansion device.The device
>> supports a keypad scan matrix of 23*8.Thi
This patch fixes a bug that the last symbol in the .symtab section of
kernel modules is not displayed with /proc/kallsyms. This happens
because the first symbol is processed twice before and inside the loop
without incrementing "src".
This bug exists since the following commit was introduced.
m
Whee -- SHA-3 is out! I wanted to explore the new toy a bit, and
so, here is a blatantly untested rough draft of SHA-3 kernel support.
Why rough draft? Because answers to the questions below will inform a
more polished version.
Code notes and questions:
1) tcrypt setup blatantly wrong. What
On 10/02/2012 10:28 PM, Matthew Garrett wrote:
> On Tue, Oct 02, 2012 at 11:13:17PM -0600, Thavatchai Makphaibulchoke wrote:
>
>> Sounds like a better solution is to allow accesses to only I/O regions
>> presented in the EFI memory map for physical addresses below 1 MB.
>
> That won't work - unf
On Tue, 2 Oct 2012, Kees Cook wrote:
> >> In the paranoid case of sysctl kernel.kptr_restrict=2, mask the kernel
> >> virtual addresses in /proc/vmallocinfo too.
> >>
> >> Reported-by: Brad Spengler
> >> Signed-off-by: Kees Cook
> >
> > /proc/vmallocinfo is S_IRUSR, not S_IRUGO, so exactly what
Hi all,
Well, here we are at another merge window and the kvmtool tree is still
not merged. So, is it likely that it will be merged in this merge
window? or the next? If not, can I please remove it from linux-next
(and have it removed from the auto-latest branch of the tip tree) as it
just adds
On Tue, Oct 02, 2012 at 11:13:17PM -0600, Thavatchai Makphaibulchoke wrote:
> Sounds like a better solution is to allow accesses to only I/O regions
> presented in the EFI memory map for physical addresses below 1 MB.
That won't work - unfortunately we do still need the low region to be
availab
On 10/02/2012 10:15 PM, Matthew Garrett wrote:
> On Tue, Oct 02, 2012 at 09:44:16PM -0700, H. Peter Anvin wrote:
>
>> We *always* expose the I/O regions to /dev/mem. That is what /dev/mem
>> *does*. The above is an exception (which is really obsolete, too: we
>> should simply disallow access to
On 02.10.2012 23:59, Jeff Garzik wrote:
> On 10/02/2012 03:44 PM, Michael Tokarev wrote:
>> On 02.10.2012 23:40, Jeff Garzik wrote:
>>
>>> Minor libata updates, nothing notable.
>>>
>>> 1) Apply -- and then revert -- the FUA feature. Caused
>>> disk corruption in linux-next, proving it cannot
Thank you both for the comments.
Sounds like a better solution is to allow accesses to only I/O regions
presented in the EFI memory map for physical addresses below 1 MB.
Do we need to worry about the X checksum in the first MB on an EFI system?
Thanks,
Mak.
On 10/02/2012 11:15 PM, Matthew Ga
On 09/30/2012 11:02 AM, Alessandro Rubini wrote:
>> I think this would be less controversial if the run-time default were
>> to disable the feature.
>
> Yes, that's the common sensible path
Fixed, there's no way I can test it well enough for anything more widespread.
> Then, I think it would be g
On Tue, Oct 02, 2012 at 09:44:16PM -0700, H. Peter Anvin wrote:
> We *always* expose the I/O regions to /dev/mem. That is what /dev/mem
> *does*. The above is an exception (which is really obsolete, too: we
> should simply disallow access to anything which is treated as system
> RAM, which doesn
On Tue, Oct 2, 2012 at 10:12 PM, David Rientjes wrote:
> On Tue, 2 Oct 2012, Kees Cook wrote:
>
>> In the paranoid case of sysctl kernel.kptr_restrict=2, mask the kernel
>> virtual addresses in /proc/vmallocinfo too.
>>
>> Reported-by: Brad Spengler
>> Signed-off-by: Kees Cook
>
> /proc/vmalloci
On Tue, 2 Oct 2012, Kees Cook wrote:
> In the paranoid case of sysctl kernel.kptr_restrict=2, mask the kernel
> virtual addresses in /proc/vmallocinfo too.
>
> Reported-by: Brad Spengler
> Signed-off-by: Kees Cook
/proc/vmallocinfo is S_IRUSR, not S_IRUGO, so exactly what are you trying
to pr
On Tue, Oct 02, 2012 at 11:33:27PM -0400, Vivien Didelot wrote:
> From: Guillaume Roguez
>
> The ADS7830 device is almost the same as the ADS7828,
> except that it does 8-bit sampling, instead of 12-bit.
> This patch extends the ads7828 driver to support this chip.
>
> Signed-off-by: Guillaume R
On Fri, 28 Sep 2012, Glauber Costa wrote:
> There was a general sentiment in a recent discussion (See
> https://lkml.org/lkml/2012/9/18/258) that the __GFP flags should be
> defined unconditionally. Currently, the only offender is GFP_NOTRACK,
> which is conditional to KMEMCHECK.
>
> This simple
On Fri, 28 Sep 2012, Fengguang Wu wrote:
> Acked-by: Glauber Costa
> Signed-off-by: Fengguang Wu
Acked-by: David Rientjes
I think init_kmem_cache_cpus() would also benefit from just being inlined
into alloc_kmem_cache_cpus().
--
To unsubscribe from this list: send the line "unsubscribe linux-
On Tue, Oct 02, 2012 at 11:33:26PM -0400, Vivien Didelot wrote:
> * Remove module parameters, add a ads7828_platform_data;
> * Move driver declaration to avoid adding function prototypes;
> * Remove unused macros;
> * Coding Style fixes.
>
> Signed-off-by: Vivien Didelot
Hi Vivien,
nice cleanup
On Tue, Oct 2, 2012 at 4:35 AM, James Morris wrote:
> Highlights:
>
> - Integrity: add local fs integrity verification to detect offline attacks
> - Integrity: add digital signature verification
Ok, the integrity changes in particular clashed with the new user
namespace support by Eric Biederman.
On 10/02/2012 09:31 PM, Matthew Garrett wrote:
> On Tue, Oct 02, 2012 at 02:50:09PM -0700, H. Peter Anvin wrote:
>
>> That sounds like exactly the opposite of normal /dev/mem behavior... we
>> allow access to non-memory resources (which really could do anything if
>> misused), but not memory.
>
>
On 2 October 2012 11:11, MyungJoo Ham wrote:
>> On 27 September 2012 13:50, MyungJoo Ham wrote:
>> >> Prepare devfreq core framework to support devices which
>> >> can idle. When device idleness is detected perhaps through
>> >> runtime-pm, need some mechanism to suspend devfreq load
>> >> monito
> On Wed, Oct 3, 2012 at 9:24 AM, Arun MURTHY
> wrote:
> >> On Mon, Oct 01, 2012 at 07:30:38AM +0200, Arun MURTHY wrote:
> >> > > On Fri, Sep 28, 2012 at 01:35:01PM +0530, Arun Murthy wrote:
> >> > > > +#include
> >> > > > +#include
> >> > > > +#include
> >> > > > +#include
> >> > > > +#includ
On Tue, Oct 02, 2012 at 02:50:09PM -0700, H. Peter Anvin wrote:
> That sounds like exactly the opposite of normal /dev/mem behavior... we
> allow access to non-memory resources (which really could do anything if
> misused), but not memory.
>From arch/x86/mm/init.c:
* On x86, access has to be gi
Hi Anton,
Today's linux-next merge of the battery tree got a conflict in
include/linux/mfd/88pm860x.h between commit 2e57d56747e6 ("mfd: 88pm860x:
Device tree support") from the mfd tree and commit a830d28b48bf
("power_supply: Enable battery-charger for 88pm860x") from the battery
tree.
I fixed i
On Tue, 2012-10-02 at 14:43 -0700, Nishanth Aravamudan wrote:
>
> Started looking into this. If your suspicion were accurate, wouldn't
> the
> bisection have stopped at 0e4bc95d87394364f408627067238453830bdbf3
> ("powerpc/iommu: Reduce spinlock coverage in iommu_alloc and
> iommu_free")?
>
> Alex
From: "Justin P. Mattock"
Signed-off-by: Justin P. Mattock
---
The patch below fixes typos while reading through staging "xgifb".
drivers/staging/xgifb/TODO |2 +-
drivers/staging/xgifb/vb_setmode.c |4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drive
On Wed, Oct 3, 2012 at 9:24 AM, Arun MURTHY wrote:
>> On Mon, Oct 01, 2012 at 07:30:38AM +0200, Arun MURTHY wrote:
>> > > On Fri, Sep 28, 2012 at 01:35:01PM +0530, Arun Murthy wrote:
>> > > > +#include
>> > > > +#include
>> > > > +#include
>> > > > +#include
>> > > > +#include
>> > > > +
>> >
On 10/03/2012 09:37 AM, Paul E. McKenney wrote:
> On Wed, Oct 03, 2012 at 09:29:01AM +0530, Srivatsa S. Bhat wrote:
>> On 10/03/2012 05:01 AM, Paul E. McKenney wrote:
>>> On Tue, Oct 02, 2012 at 11:58:36PM +0200, Jiri Kosina wrote:
On Tue, 2 Oct 2012, Jiri Kosina wrote:
1331e7a1b
Hi Samuel,
Today's linux-next merge of the mfd tree got a conflict in
drivers/video/backlight/88pm860x_bl.c between commit e1c9ac420ef1
("Revert "backlight: fix memory leak on obscure error path"") from Linus'
tree and commit a6ccdcd98c39 ("mfd: 88pm860x: Use REG resource for
backlight") from the
Cleans up the builtin-kvm code in preparation for the live mode.
No functional changes; only code movement.
Signed-off-by: David Ahern
Cc: Dong Hao
Cc: Runzhen Wang
Cc: Xiao Guangrong
Cc: Ingo Molnar
---
tools/perf/builtin-kvm.c | 460 +-
1 file c
On Wed, Oct 03, 2012 at 09:29:01AM +0530, Srivatsa S. Bhat wrote:
> On 10/03/2012 05:01 AM, Paul E. McKenney wrote:
> > On Tue, Oct 02, 2012 at 11:58:36PM +0200, Jiri Kosina wrote:
> >> On Tue, 2 Oct 2012, Jiri Kosina wrote:
> >>
> >> 1331e7a1bbe1f11b19c4327ba0853bee2a606543 is the first bad co
On 10/03/2012 09:14 AM, Paul E. McKenney wrote:
> On Wed, Oct 03, 2012 at 09:05:31AM +0530, Srivatsa S. Bhat wrote:
>> On 10/03/2012 03:47 AM, Jiri Kosina wrote:
>>> On Wed, 3 Oct 2012, Srivatsa S. Bhat wrote:
>>>
I don't see how this circular locking dependency can occur.. If you are
us
On 10/03/2012 05:01 AM, Paul E. McKenney wrote:
> On Tue, Oct 02, 2012 at 11:58:36PM +0200, Jiri Kosina wrote:
>> On Tue, 2 Oct 2012, Jiri Kosina wrote:
>>
>> 1331e7a1bbe1f11b19c4327ba0853bee2a606543 is the first bad commit
>> commit 1331e7a1bbe1f11b19c4327ba0853bee2a606543
>> Author: P
Hi Chen,
2012/10/03 11:12, Ni zhan Chen wrote:
On 10/03/2012 09:21 AM, Yasuaki Ishimatsu wrote:
Hi Andrew,
2012/10/03 6:42, Andrew Morton wrote:
On Tue, 2 Oct 2012 17:25:06 +0900
Yasuaki Ishimatsu wrote:
remove_memory() offlines memory. And it is called by following two cases:
1. echo off
> On Mon, Oct 01, 2012 at 07:30:38AM +0200, Arun MURTHY wrote:
> > > On Fri, Sep 28, 2012 at 01:35:01PM +0530, Arun Murthy wrote:
> > > > +#include
> > > > +#include
> > > > +#include
> > > > +#include
> > > > +#include
> > > > +
> > > > +static struct class *modem_class;
> > >
> > > What's wr
On 10/03/2012 06:15 AM, Jiri Kosina wrote:
> On Tue, 2 Oct 2012, Paul E. McKenney wrote:
>
>> On Wed, Oct 03, 2012 at 01:48:21AM +0200, Jiri Kosina wrote:
>>> On Tue, 2 Oct 2012, Paul E. McKenney wrote:
>>>
Indeed. Slab seems to be doing an rcu_barrier() in a CPU hotplug
notifier, whic
On 10/02/2012 07:43 PM, Jonathan McDowell wrote:
> Upgraded to 3.6 today on my dev box and after seeing an FC attached SAN
> go down and come back up (due to an expected reboot) I started getting
> the following in my logs. It continues even after the array is back and
> functioning - I'm seeing:
>
On Wed, Oct 03, 2012 at 09:05:31AM +0530, Srivatsa S. Bhat wrote:
> On 10/03/2012 03:47 AM, Jiri Kosina wrote:
> > On Wed, 3 Oct 2012, Srivatsa S. Bhat wrote:
> >
> >> I don't see how this circular locking dependency can occur.. If you are
> >> using SLUB,
> >> kmem_cache_destroy() releases slab_
Adding Martin to the cc, so he can chime in on WRITE_SAME if I got it
wrong
On Wed, Oct 03, 2012 at 01:30:45PM +1000, NeilBrown wrote:
> On Tue, 2 Oct 2012 14:09:23 -0700 Kent Overstreet
> wrote:
>
> > On Tue, Oct 02, 2012 at 04:22:01PM +1000, NeilBrown wrote:
> > > On Fri, 28 Sep 2012 09:23:43
On Wed, Oct 03, 2012 at 02:45:30AM +0200, Jiri Kosina wrote:
> On Tue, 2 Oct 2012, Paul E. McKenney wrote:
>
> > On Wed, Oct 03, 2012 at 01:48:21AM +0200, Jiri Kosina wrote:
> > > On Tue, 2 Oct 2012, Paul E. McKenney wrote:
> > >
> > > > Indeed. Slab seems to be doing an rcu_barrier() in a CPU h
On Sun, Jul 22, 2012 at 1:16 PM, Bret Towe wrote:
> just booted a fresh 3.5 kernel and got the following on login via gdm
> on the client computer
> didn't see any crashes yet on any other computer but didn't give it
> long to try after seeing this
> let me know if you need more info
> this client
On 10/03/2012 03:47 AM, Jiri Kosina wrote:
> On Wed, 3 Oct 2012, Srivatsa S. Bhat wrote:
>
>> I don't see how this circular locking dependency can occur.. If you are
>> using SLUB,
>> kmem_cache_destroy() releases slab_mutex before it calls rcu_barrier(). If
>> you are
>> using SLAB, kmem_cache_
* Remove module parameters, add a ads7828_platform_data;
* Move driver declaration to avoid adding function prototypes;
* Remove unused macros;
* Coding Style fixes.
Signed-off-by: Vivien Didelot
---
Documentation/hwmon/ads7828 | 31 +++--
drivers/hwmon/ads7828.c | 206 +
From: Guillaume Roguez
The ADS7830 device is almost the same as the ADS7828,
except that it does 8-bit sampling, instead of 12-bit.
This patch extends the ads7828 driver to support this chip.
Signed-off-by: Guillaume Roguez
Signed-off-by: Vivien Didelot
---
Documentation/hwmon/ads7828 | 12 ++
Add Chris in mail loop.
Best Regards,
Alexandra Chin
Synaptics Hong Kong Limited, Taiwan Branch
5F., No. 501, Sec. 2 Tiding Blvd., Neihu District,
Taipei City 114, Taiwan
Office: 886.2.8752.5700 ext:652
Email:alexandra.c...@synaptics.com.tw
-Original Message-
From: Alexandra Chin
On Tue, 2 Oct 2012 14:09:23 -0700 Kent Overstreet
wrote:
> On Tue, Oct 02, 2012 at 04:22:01PM +1000, NeilBrown wrote:
> > On Fri, 28 Sep 2012 09:23:43 -0700 Kent Overstreet
> > wrote:
> >
> > > On Mon, Sep 24, 2012 at 02:56:39PM +1000, NeilBrown wrote:
> > > >
> > > > Hi Jens,
> > > > this pa
On Tue, Oct 2, 2012 at 5:11 PM, Andy Shevchenko
wrote:
> There are few cleanups to the driver which already acked and reviewed.
> I decide to split last series to two parts. This is first part.
Looks good.
Acked-by: Viresh Kumar
--
To unsubscribe from this list: send the line "unsubscribe linux
On Tue, Oct 02, 2012 at 10:28:13PM -0400, Vivien Didelot wrote:
> Hi Guenter,
>
> Some of those changes weren't in the mainline tree a few days ago.
> I'll cherry-pick them and send a update very soon :-)
>
True, but they have been in -next for the last two months or so ...
Guenter
--
To unsubsc
Hi Benjamin,
I have one little question about __i2chid_command(), please see below.
"benjamin.tissoires" writes:
> From: Benjamin Tissoires
>
> Microsoft published the protocol specification of HID over i2c:
> http://msdn.microsoft.com/en-us/library/windows/hardware/hh852380.aspx
>
> This patch
On Wed, Oct 03, 2012 at 10:41:06AM +0900, Tejun Heo wrote:
> Hello, Kent.
>
> On Tue, Oct 02, 2012 at 02:41:13PM -0700, Kent Overstreet wrote:
> > Seems to me it'd be no different from security considerations when
> > introducing new ioctls. I.e., messy, ad hoc, easy to get wrong, but
> > sometime
Remove the pSeries_reconfig.h header file. At this point there is only one
definition in the file, pSeries_coalesce_init(), which can be
moved to rtas.h.
Signed-off-by: Nathan Fontenot
---
arch/powerpc/include/asm/pSeries_reconfig.h | 15 ---
arch/powerpc/include/asm/rtas.h
Rename the prom_*_property routines of the generic OF code to of_*_property.
This brings them in line with the naming used by the rest of the OF code.
Signed-off-by: Nathan Fontenot
---
arch/powerpc/kernel/machine_kexec.c | 12 ++--
arch/powerpc/kernel/machine_kexec_64.c|
This patch moves the notification chain for updates to the device tree
from the powerpc/pseries code to the base OF code. This makes this
functionality available to all architectures.
Additionally the notification chain is updated to allow notifications
for property add/remove/update. To make this
This patch moves the definition of the of_drconf_cell struct to asm/prom.h
to make it available for all powerpc/pseries code.
Signed-off-by: Nathan Fontenot
---
arch/powerpc/include/asm/prom.h | 16
arch/powerpc/mm/numa.c | 12
2 files changed, 16 ins
When adding or removing a device tree node we should also update
the device tree in /proc/device-tree. This action is already done in the
generic OF code for adding/removing properties of a node. This patch adds
this functionality for nodes.
Signed-off-by: Nathan Fontenot
---
arch/powerpc/platf
On Tue, Oct 02, 2012 at 07:31:58PM -0700, Linus Torvalds wrote:
> On Tue, Oct 2, 2012 at 6:39 PM, Al Viro wrote:
> > This is *not* all; fs/dcache.c bits will go separately, for one
> > thing - that's just the first pile. Please, pull from the usual place -
>
> Al, *please* describe what
On Wed, Oct 03, 2012 at 11:28:25AM +1000, Dave Chinner wrote:
> On Tue, Oct 02, 2012 at 05:20:29PM -0700, Kent Overstreet wrote:
> > On Tue, Oct 02, 2012 at 01:41:17PM -0400, Jeff Moyer wrote:
> > > Kent Overstreet writes:
> > >
> > > > So, I and other people keep running into things where we rea
From: Tao Hou
Date: Tue, 2 Oct 2012 10:42:43 +0800
> chan->count is used by rx channel. If the desc count is not updated by
> the clean up loop in cpdma_chan_stop, the value written to the rxfree
> register in cpdma_chan_start will be incorrect.
>
> Signed-off-by: Tao Hou
Applied, thanks.
--
On Tue, Oct 2, 2012 at 6:39 PM, Al Viro wrote:
> This is *not* all; fs/dcache.c bits will go separately, for one
> thing - that's just the first pile. Please, pull from the usual place -
Al, *please* describe what is going on. Your description is negative
(what *doesn't* happen in this p
Hi Guenter,
Some of those changes weren't in the mainline tree a few days ago.
I'll cherry-pick them and send a update very soon :-)
Thanks for the tips,
Vivien
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More ma
ivers/mtd/ubi/ubi.ko] undefined!
I have used the ubi tree form next-20121002 for today.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
pgpggJOs1F8TF.pgp
Description: PGP signature
Fix below issues:
1. If request_threaded_irq() fails, current code does not free all requested
irqs.
2. Add missing extcon_dev_unregister() in error path if failed to read revision
number.
Signed-off-by: Axel Lin
---
drivers/extcon/extcon-max77693.c | 12 ++--
1 file changed, 6 i
From: Haicheng Li
Date: Fri, 28 Sep 2012 14:57:38 +0800
> On 09/28/2012 02:46 PM, David Miller wrote:
>> From: Haicheng Li
>> Date: Fri, 28 Sep 2012 14:41:43 +0800
>>
>>> On 09/28/2012 06:09 AM, David Miller wrote:
Look at how other people submit patches, do any other patch
submissions
On 10/03/2012 09:21 AM, Yasuaki Ishimatsu wrote:
Hi Andrew,
2012/10/03 6:42, Andrew Morton wrote:
On Tue, 2 Oct 2012 17:25:06 +0900
Yasuaki Ishimatsu wrote:
remove_memory() offlines memory. And it is called by following two
cases:
1. echo offline >/sys/devices/system/memory/memoryXX/state
Hello, Kent.
On Tue, Oct 02, 2012 at 02:41:13PM -0700, Kent Overstreet wrote:
> Seems to me it'd be no different from security considerations when
> introducing new ioctls. I.e., messy, ad hoc, easy to get wrong, but
> sometimes no way around it.
>
> It really has to be ad hoc if it's extensible,
This is *not* all; fs/dcache.c bits will go separately, for one
thing - that's just the first pile. Please, pull from the usual place -
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
Shortlog:
Al Viro (67):
do_add_mount()/umount -l races
close the race in
On Tue, Oct 02, 2012 at 05:20:29PM -0700, Kent Overstreet wrote:
> On Tue, Oct 02, 2012 at 01:41:17PM -0400, Jeff Moyer wrote:
> > Kent Overstreet writes:
> >
> > > So, I and other people keep running into things where we really need to
> > > add an interface to pass some auxiliary... stuff along
Hi Andrew,
2012/10/03 6:42, Andrew Morton wrote:
On Tue, 2 Oct 2012 17:25:06 +0900
Yasuaki Ishimatsu wrote:
remove_memory() offlines memory. And it is called by following two cases:
1. echo offline >/sys/devices/system/memory/memoryXX/state
2. hot remove a memory device
In the 1st case, the
Upgraded to 3.6 today on my dev box and after seeing an FC attached SAN
go down and come back up (due to an expected reboot) I started getting
the following in my logs. It continues even after the array is back and
functioning - I'm seeing:
kernel:[109104.348034] BUG: soft lockup - CPU#6 stuck fo
Sascha,
On Tue, Oct 2, 2012 at 2:32 AM, Evgeniy Polyakov wrote:
> On Mon, Oct 01, 2012 at 02:51:44PM -0300, Fabio Estevam
> (fabio.este...@freescale.com) wrote:
>> Evgeny,
>>
>> Any comments, please?
>
> I have no objections per se, but I'm hardly an expert in imx clock
> framework :)
>
> Since
On Mon, 01 Oct 2012 11:03:21 +0100, Mark Brown said:
> On Sun, Sep 30, 2012 at 12:15:55PM +0200, Paul Bolle wrote:
> > Building regmap.o triggers this GCC warning:
> > drivers/base/regmap/regmap.c: In function âregmap_raw_readâ:
> > drivers/base/regmap/regmap.c:1172:6: warning: âretâ
(2012/10/03 4:37), Andi Kleen wrote:
Takao Indoh writes:
These patches reset PCIe devices at boot time to address DMA problem on
kdump with iommu. When "reset_devices" is specified, a hot reset is
triggered on each PCIe root port and downstream port to reset its
downstream endpoint.
Great. I
Hello,
On Tue, Oct 02, 2012 at 09:26:03AM -0400, Vivek Goyal wrote:
> Yes this one is little odd. Ok, I will change it back to "service_tree"
> and only use "st" for local variables and in some function names.
Yes, please do that. In general, it's beneficial to use at least
somewhat descriptive
On Mon, Oct 01, 2012 at 03:32:42PM -0400, Vivek Goyal wrote:
> Currently CFQ has three IO classes, RT, BE and IDLE. At many a places we
> are calling workloads belonging to these classes as "prio". This gets
> very confusing as one starts to associate it with ioprio.
>
> So this patch just does bu
From: Andrew Morton
Date: Tue, 2 Oct 2012 15:55:44 -0700
> I had a shot at integrating all this onto the pending stuff in linux-next.
> "mm: Add and use update_mmu_cache_pmd() in transparent huge page code."
> needed minor massaging in huge_memory.c. But as Andrea mentioned, we
> ran aground on
From: Ben Hutchings
Date: Wed, 03 Oct 2012 01:17:12 +0100
> On Tue, 2012-10-02 at 23:06 +0400, Michael Tokarev wrote:
>> On 02.10.2012 22:49, Ferenc Wagner wrote:
>> > "Michael Chan" writes:
>> >> These are the likely fixes:
>> >>
>> >> commit cf9ecf4b631f649a964fa611f1a5e8874f2a76db
>> >> Auth
On Tue, 2 Oct 2012, Paul E. McKenney wrote:
> On Wed, Oct 03, 2012 at 01:48:21AM +0200, Jiri Kosina wrote:
> > On Tue, 2 Oct 2012, Paul E. McKenney wrote:
> >
> > > Indeed. Slab seems to be doing an rcu_barrier() in a CPU hotplug
> > > notifier, which doesn't sit so well with rcu_barrier() tryi
1 - 100 of 633 matches
Mail list logo
