On 11/29/2012 10:43 AM, Greg Kroah-Hartman wrote:
-/* Used for HOTPLUG */
-#define __devinit__section(.devinit.text) __cold notrace
-#define __devinitdata__section(.devinit.data)
-#define __devinitconst __constsection(.devinit.rodata)
-#define __devexit__section(.devexit.te
> -Original Message-
> From: H. Peter Anvin [mailto:h...@zytor.com]
> Sent: Friday, November 30, 2012 11:46 AM
> To: Yu, Fenghua
> Cc: Ingo Molnar; Thomas Gleixner; Mallick, Asit K; Tigran Aivazian;
> Andreas Herrmann; Borislav Petkov; linux-kernel; x86
> Subject: Re: [PATCH v2 01/10] Docum
On 11/29/2012 10:43 AM, Greg Kroah-Hartman wrote:
From: Greg Kroah-Hartman
With the recent work to remove CONFIG_HOTPLUG, we are starting to get a
bunch of __devinit section warnings, despite CONFIG_HOTPLUG always being
enabled. So, stop marking the sections entirely, by defining them away
the
On Fri, Nov 30, 2012 at 11:58 AM, Ingo Molnar wrote:
>
> When pushed hard enough via threaded workloads (for example via the
> numa02 test) then the upstream page migration code in mm/migration.c
> becomes unscalable, resulting in lot of scheduling on the anon vma
> mutex and a subsequent drop in
> 2012/11/30, Greg KH :
> For some reason you sent this only to me, which is a bit rude to
> everyone else on the mailing list. I'll be glad to respond if you
> resend it to everyone.
Sorry, seem's i've reply instead of reply to all.
Anyway, it's maybe not the better idea i've had this day, but i
> -Original Message-
> From: Michal Nazarewicz [mailto:m...@google.com] On Behalf Of Michal
> Nazarewicz
> Sent: Friday, November 30, 2012 10:01 AM
> To: Andrianov, Vitaly; m.szyprow...@samsung.com;
> kyungmin.p...@samsung.com; a...@arndb.de; linux-kernel@vger.kernel.org;
> linux-keyst...
On Wed, Nov 28, 2012 at 08:54:14PM +0800, Xiao Guangrong wrote:
> vmcs->cpu indicates whether it exists on the target cpu, -1 means the vmcs
> does not exist on any vcpu
>
> If vcpu load vmcs with vmcs.cpu = -1, it can be directly added to cpu's percpu
> list. The list can be corrupted if the cpu
On Thu, Nov 29, 2012 at 02:07:59PM -0700, Alex Williamson wrote:
> Prior to memory slot sorting this loop compared all of the user memory
> slots for overlap with new entries. With memory slot sorting, we're
> just checking some number of entries in the array that may or may not
> be user slots.
On Fri, Nov 30, 2012 at 11:18 AM, Luis R. Rodriguez
wrote:
> On Fri, Nov 30, 2012 at 12:38 AM, Arend van Spriel wrote:
>> So what is the rationale here. During mainlining our drivers we had to
>> remove all uses of 'typedef struct foo foo_t;'. The Linux CodingStyle
>> (chapter 5 Typedefs) is spen
When a cpu enters S3 state, the FPU state is lost.
After resuming for S3, if we try to lazy restore the FPU for a process running
on the same CPU, this will result in a corrupted FPU context.
Ensure that "fpu_owner_task" is properly invalided when (re-)initializing a CPU,
so nobody will try to laz
On Fri, 30 Nov 2012 12:36:35 +0100 (CET)
Lukáš Czerner wrote:
> On Fri, 30 Nov 2012, Andrew Morton wrote:
>
> > Date: Fri, 30 Nov 2012 02:48:42 -0800
> > From: Andrew Morton
> > To: Lukas Czerner
> > Cc: linux-kernel@vger.kernel.org, linux-r...@vger.kernel.org,
> > ax...@kernel.dk,
> > jm
On Friday, November 30, 2012 10:57:55 AM Greg KH wrote:
> On Fri, Nov 30, 2012 at 10:45:44AM -0800, Dmitry Torokhov wrote:
> > However you snipped the rest of my reply: do we really need to renumber
> > ioctls? There is no benefit for the driver as its ioctl handler does
> > not parse the numbers i
From: Haiyang Zhang
Date: Fri, 30 Nov 2012 11:23:41 -0800
> This message indicates an error returned from the host when changing MAC
> address.
>
> Reported-by: Michal Kubecek
> Signed-off-by: Haiyang Zhang
> Reviewed-by: K. Y. Srinivasan
Applied.
--
To unsubscribe from this list: send the
As an implementational detail, to be able to do directed task placement
we have to change how task_numa_fault() interfaces with the scheduler:
instead of the placement logic being executed directly from the fault
path we now trigger a worklet, similarly to how we do the NUMA
hinting fault work.
Th
NUMA balancing will make use of the new sched_rebalance_to() mode:
the ability to 'flip' two tasks.
When two tasks have a similar weight but one of them executes on
the wrong CPU or node, then it's beneficial to do a quick flipping
operation. This will not change the general load of the source
and
I'm pleased to announce the latest, -v18 numa/core release.
This release fixes regressions and improves NUMA performance.
It has the following main changes:
- Introduce directed NUMA convergence, which is based on
the 'task buddy' relation introduced in -v17, and make
use of the new "ta
Reduce the 4K page fault count by looking around and processing
nearby pages if possible.
To keep the logic and cache overhead simple and straightforward
we do a couple of simplifications:
- we only scan in the HPAGE_SIZE range of the faulting address
- we only go as far as the vma allows us
A
On Friday 30 November 2012 02:22 PM, Axel Lin wrote:
If pdata->base_voltage_uV is missing or the settings of pdata->base_voltage_uV
and pdata->max_voltage_uV are out of range, TPS51632_VOLT_VSEL macro
returns wrong vsel.
Thus add checking [base|max]_voltage_uV pdata settings in probe.
Looks g
From: Ben Hutchings
Date: Fri, 30 Nov 2012 19:14:40 +
> On Fri, 2012-11-30 at 12:23 -0500, David Miller wrote:
>> From: Jiri Kosina
>> Date: Fri, 30 Nov 2012 16:23:30 +0100 (CET)
>>
>> > Of course it'd be far better if faulty hardware can be autodetected in
>> > runtime.
>>
>> That is how
Remove leftovers of the (now inactive) statistical NUMA scheduling code.
Cc: Linus Torvalds
Cc: Andrew Morton
Cc: Peter Zijlstra
Cc: Andrea Arcangeli
Cc: Rik van Riel
Cc: Mel Gorman
Cc: Hugh Dickins
Signed-off-by: Ingo Molnar
---
include/linux/sched.h | 2 -
kernel/sched/core.c |
Zhouping Liu reported worse out-of-memory behavior with
CONFIG_NUMA_BALANCING=y, compared to the mainline kernel.
One reason for that change in behavior is that with typical
applications the mainline kernel allocates memory essentially
randomly, and leaves it where it was.
"Random" placement is n
Track strength of convergence, which is a value between 1 and 1024.
This will be used by the placement logic later on.
A strength value of 1024 means that the workload has fully
converged, all faults after the last scan period came from a
single node.
A value of 1024/nr_nodes means a totally spre
Mel Gorman reported that the NUMA code is system-time intense even
after a workload has converged.
To remedy this, turn sched_numa_scan_size into a range:
sched_numa_scan_size_min[default: 32 MB]
sched_numa_scan_size_max[default: 512 MB]
As workloads converge, so does thei
Change the adaptive memory policy code to take a majority of buddies
on a node into account. Previously, since this commit:
"sched: Track shared task's node groups and interleave their memory
allocations"
We'd include any node that has run a buddy in the past, which was too
aggressive and spre
Consolidate the various convergence models and add a new one: when
a strongly converged NUMA task migrates, prefer to migrate it in
the direction of its preferred node.
Cc: Linus Torvalds
Cc: Andrew Morton
Cc: Peter Zijlstra
Cc: Andrea Arcangeli
Cc: Rik van Riel
Cc: Mel Gorman
Cc: Hugh Dicki
This patch replaces the purely statistical NUMA convergence
method with a directed one.
These balancing functions gets called when CPU loads are otherwise
more or less in balance, so we check whether a NUMA task wants
to migrate to another node, to improve NUMA task group clustering.
Our general
On 11/30/2012 11:54 AM, Vincent Palatin wrote:
>>
> I have done a patch v2 according to your suggestions.
> I will run the testing on it now.
> I probably need at least 2 to 3 hours to validate it.
>
That would be super. Let me know and I'll queue it up and send a pull
request with this and a fe
When a cpu enters S3 state, the FPU state is lost.
After resuming for S3, if we try to lazy restore the FPU for a process running
on the same CPU, this will result in a corrupted FPU context.
Ensure that "fpu_owner_task" is properly invalided when (re-)initializing a CPU,
so nobody will try to laz
On 11/30/2012 11:41 AM, Linus Torvalds wrote:
>>
>> Hmm... from my point of view it would almost seem saner to do this on
>> the way *up*... as part of CPU (re-)initialization. After all, the
>> "nothing is currently running on this CPU" is part of the initial state
>> of the CPU, regardless of if
On Fri, Nov 30, 2012 at 11:38 AM, H. Peter Anvin wrote:
> On 11/30/2012 11:25 AM, Linus Torvalds wrote:
>>
>> and in fact I think the right place to do this *might* be in
>> "native_cpu_die()" instead, at which point it would actually be
>> something like
>>
>> per_cpu(fpu_owner_task, cpu) = N
>From 879a3d9dbbde823ac77d39131e7a287f31b8296f Mon Sep 17 00:00:00 2001
From: Gao feng
Date: Sat, 1 Dec 2012 00:21:28 +0800
cgroup_clear_directory() incorrectly invokes cgroup_rm_file() on each
cftset of the target subsystems, which only removes the first file of
each set. This leaves dangling f
On 11/29/2012 05:47 PM, Fenghua Yu wrote:
> +
> +mkdir initrd
> +cd initrd
> +cp ../microcode.hex kernel/x86/microcode/GenuineIntel/microcode.hex
> +find .|cpio -oc >../ucode.cpio
> +cd ..
> +cat ucode.cpio /boot/initrd-3.5.0.img >/boot/initrd-3.5.0.ucode.img
> +
> +The generated /boot/initrd-3.5.0
Fix call to line discipline receive_buf by synclink drivers.
Dummy flag buffer argument is ignored by N_HDLC line discipline but might
be of insufficient size if accessed by a different line discipline
selected by mistake. Calls are changed to use data buffer argument for
both data and flag buffer
On Fri, Nov 30, 2012 at 10:38 AM, Frederic Weisbecker
wrote:
> 2012/11/28 Hakan Akkan :
>> +static int check_drop_timer_duty(int cpu)
>> +{
>> + int curr_handler, prev_handler, new_handler;
>> + int nrepeat = -1;
>> + bool drop_recheck;
>> +
>> +repeat:
>> + WARN_ON_ONCE(++
On 11/30/2012 11:25 AM, Linus Torvalds wrote:
>
> and in fact I think the right place to do this *might* be in
> "native_cpu_die()" instead, at which point it would actually be
> something like
>
> per_cpu(fpu_owner_task, cpu) = NULL;
>
> *after* the CPU is dead, so that nothing ever can act
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: James Bottomley
commit 949a05d03490e39e773e8652ccab9157e6f595b4 upstream.
On Thu, 2012-11-01 at 16:45 -0700, Michel Lespinasse wrote:
> Looking at the arch/parisc/kernel/sys_parisc.c implementa
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jiri Engelthaler
commit c36a7ff4578ab6294885aef5ef241aeec4cdb1f0 upstream.
Fixed parsing end absolute address.
Signed-off-by: Jiri Engelthaler
Signed-off-by: Artem Bityutskiy
Signed-off-by:
On 11/30/2012 09:01 AM, Rob Herring wrote:
> On 11/27/2012 05:29 PM, Stephen Warren wrote:
>> From: Stephen Warren
>>
>> All architectures that use cmd_dtc do so in almost the same way. Create
>> a central build rule to avoid duplication. The one difference is that
>> most current uses of dtc buil
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jens Axboe
commit a8c32a5c98943d370ea606a2e7dc04717eb92206 upstream.
Request based dm attempts to re-run the request queue off the
request completion path. If used with a driver that potentiall
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Darren Hart
commit aa10990e028cac3d5e255711fb9fb47e00700e35 upstream.
Dave Jones reported a bug with futex_lock_pi() that his trinity test
exposed. Sometime between queue_me() and taking the q
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: David Henningsson
commit 34c3d1926bdaf45d3a891dd577482abcdd9faa34 upstream.
If this array is not cleared, the jack related code later might
fail to create "Internal Speaker Phantom Jack" on Del
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Simon Wunderlich
commit b78a4932f5fb11fadf41e69c606a33fa6787574c upstream.
The check whether the IBSS is active and can be removed should be
performed before deinitializing the fields used for
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Bolle
commit 45171002b01b2e2ec4f991eca81ffd8430fd0aec upstream.
The Intel 82855PM host bridge / Mobility FireGL 9000 RV250 combination
in an (outdated) ThinkPad T41 needs AGPMode 1 for sus
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kailang Yang
commit 7ff34ad80b7080fafaac8efa9ef0061708eddd51 upstream.
These are compatible with standard ALC269 parser.
Signed-off-by: Kailang Yang
Signed-off-by: Takashi Iwai
Signed-off-by
On Fri, Nov 30, 2012 at 10:52 AM, Vincent Palatin wrote:
> When a cpu enters S3 state, the FPU state is lost.
> After resuming for S3, if we try to lazy restore the FPU for a process running
> on the same CPU, this will result in a corrupted FPU context.
Good catch, and I think the patch is techn
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Danny Kukawka
commit c718a54649475cc397484f96e70f6d0fdd267165 upstream.
Fix several -Wuninitialized compiler warnings by changing the
order of getting modedb in riva_update_default_var() to set
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
commit 450faacc621dbe0a4945ed8292afd45f4602d263 upstream.
Documentation/networking/ifenslave.c: In function ‘if_getconfig’:
Documentation/networking/ifenslave.c:508:14: warnin
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Danny Kukawka
commit cecd353a02fb1405c8a72a324b26b5acf97e7411 upstream.
Set CommandMailbox with memset before use it. Fix for:
drivers/block/DAC960.c: In function ‘DAC960_V1_EnableMemoryMailbo
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit 441a179dafc0f99fc8b3a8268eef66958621082e upstream.
int sys32_rt_sigprocmask(int how, compat_sigset_t __user *set, compat_sigset_t
__user *oset,
Hi Masanari,
Thanks for your patch.
> Subject: [PATCH] [trivial] wireless: mwifiex: Fix typo in wireless/mwifiex
> driver
>
> Correct spelling typo in wireless/mwifiex driver.
>
> Signed-off-by: Masanari Iida
Acked-by: Bing Zhao
Regards,
Bing
> ---
> drivers/net/wireless/mwifiex/sta_ioct
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Robert Richter
commit 1022623842cb72ee4d0dbf02f6937f38c92c3f41 upstream.
In 32 bit the stack address provided by kernel_stack_pointer() may
point to an invalid range causing NULL pointer access
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Boris Ostrovsky
commit 36c46ca4f322a7bf89aad5462a3a1f61713edce7 upstream.
Add valid patch size for family 16h processors.
[ hpa: promoting to urgent/stable since it is hw enabling and trivial
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Albert Pool
commit a485e827f07bfdd0762059386e6e787bed6e81ee upstream.
This is an ISY IWL 2000. Probably a clone of Belkin F7D1102 050d:1102.
Its FCC ID is the same.
Signed-off-by: Albert Pool
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Szymon Janc
commit 8f321f853ea0c7141977cd34804476e2e07e upstream.
If remote device sends bogus RFC option with invalid length,
undefined options values are used. Fix this by using defaults
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Mack
commit da185443c12f5ef7416af50293833a5654854186 upstream.
Fixes the following warning:
CC [M] sound/usb/caiaq/device.o
sound/usb/caiaq/device.c: In function ‘snd_probe’:
sound/u
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alexandre Pereira da Silva
commit 782759b9f5f5223e0962af60c3457c912fab755f upstream.
Fix the following compilation warning:
fs/ubifs/dir.c: In function 'ubifs_rename':
fs/ubifs/dir.c:972:15: w
On 11/29/2012 10:44 PM, Mark Zhang wrote:
> This patch adds the RGB & HDMI nodes in Tegra 30 cardhu's dts.
> This makes the LVDS & HDMI working.
This still doesn't add any of the backlight/panel GPIO programming,
which I believe is required before we enable any LCDs. We could add the
HDMI node wit
This is the start of the stable review cycle for the 3.4.21 release.
There are 56 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Dec 2 18:50:02 UTC 2012.
Anything receive
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit 25389bb207987b5774182f763b9fb65ff08761c8 upstream.
Commit 09e05d48 introduced a wait for transaction commit into
journal_unmap_buffer() in the case we are truncating a buffer un
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit 0181bd5dea2ed0696f84591a92da0b6a1f1a2e62 upstream.
Signed-off-by: Alex Deucher
Signed-off-by: Greg Kroah-Hartman
---
include/drm/drm_pciids.h |1 +
1 file changed, 1
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Clemens Ladisch
commit e99ddfde6ae0dd2662bb40435696002b590e4057 upstream.
Commit 88a8516a2128 (ALSA: usbaudio: implement USB autosuspend) added
autosuspend code to all files making up the snd-u
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: David Henningsson
commit 34c3d1926bdaf45d3a891dd577482abcdd9faa34 upstream.
If this array is not cleared, the jack related code later might
fail to create "Internal Speaker Phantom Jack" on Del
Hello, Gao.
On Sat, Dec 01, 2012 at 12:21:29AM +0800, Gao feng wrote:
> cgroup_clear_directroy is called by cgroup_d_remove_dir
> and cgroup_remount.
>
> when we call cgroup_remount to remount the cgroup,the subsystem
> may be unlinked from cgroupfs_root->subsys_list in rebind_subsystem,this
> su
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: James Bottomley
commit 949a05d03490e39e773e8652ccab9157e6f595b4 upstream.
On Thu, 2012-11-01 at 16:45 -0700, Michel Lespinasse wrote:
> Looking at the arch/parisc/kernel/sys_parisc.c implementa
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit 441a179dafc0f99fc8b3a8268eef66958621082e upstream.
int sys32_rt_sigprocmask(int how, compat_sigset_t __user *set, compat_sigset_t
__user *oset,
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Keith Busch
commit c7d36ab8fa04c213328119a9c0d66985fe204ee5 upstream.
Signed-off-by: Keith Busch
Signed-off-by: Matthew Wilcox
Signed-off-by: Greg Kroah-Hartman
---
drivers/block/nvme.c |
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Betker
commit 5ffd3412ae5536a4c57469cb8ea31887121dcb2e upstream.
jffs2_write_begin() first acquires the page lock, then f->sem. This
causes an AB-BA deadlock with jffs2_garbage_collect_l
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: majianpeng
commit ab05613a0646dcc11049692d54bae76ca9ffa910 upstream.
This bug was introduced by commit(v3.0-rc7-126-g2230dfe).
So fix is suitable for 3.0.y thru 3.6.y.
Signed-off-by: Jianpeng
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit cca85013ef54f66eb4616e6f3860549a96c8338b upstream.
We don't use "dev" any more after 07ec747a5f ("libsas: remove
ata_port.lock management duties from lldds") and it causes
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jens Axboe
commit a8c32a5c98943d370ea606a2e7dc04717eb92206 upstream.
Request based dm attempts to re-run the request queue off the
request completion path. If used with a driver that potentiall
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jiri Engelthaler
commit c36a7ff4578ab6294885aef5ef241aeec4cdb1f0 upstream.
Fixed parsing end absolute address.
Signed-off-by: Jiri Engelthaler
Signed-off-by: Artem Bityutskiy
Signed-off-by:
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Maciej Patelczyk
commit 49bd665c5407a453736d3232ee58f2906b42e83c upstream.
SATA MICROCODE DOWNALOAD fails on isci driver. After receiving Register
Device to Host (FIS 0x34) frame Initiator rese
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Bolle
commit 45171002b01b2e2ec4f991eca81ffd8430fd0aec upstream.
The Intel 82855PM host bridge / Mobility FireGL 9000 RV250 combination
in an (outdated) ThinkPad T41 needs AGPMode 1 for sus
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit 884162df2aadd7414bef4935e1a54976fd4e3988 upstream.
When a write to a replacement device completes, we carefully
and correctly found the rdev that the write actually went to
and
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Oliver Hartkopp
commit c9faaa09e2a1335678f09c70a0d0eda095564bab upstream.
The skb->tstamp is set to the hardware timestamp when available in the USB
urb message. This leads to user visible time
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Oliver Hartkopp
commit 81b401100c01d2357031e874689f89bd788d13cd upstream.
Set in the rx_ifindex to pass the correct interface index in the case of a
message timeout detection. Usually the rx_if
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit 25389bb207987b5774182f763b9fb65ff08761c8 upstream.
Commit 09e05d48 introduced a wait for transaction commit into
journal_unmap_buffer() in the case we are truncating a buffer un
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Darren Hart
commit aa10990e028cac3d5e255711fb9fb47e00700e35 upstream.
Dave Jones reported a bug with futex_lock_pi() that his trinity test
exposed. Sometime between queue_me() and taking the q
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: majianpeng
commit 35f9ac2dcec8f79d7059ce174fd7b7ee3290d620 upstream.
If read_seqretry returned true and bbp was changed, it will write
invalid address which can cause some serious problem.
Thi
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Sachin Kamat
commit 5a6ea4af0907f995dc06df21a9c9ef764c7cd3bc upstream.
The pointer returned by kzalloc should be tested for NULL
to avoid potential NULL pointer dereference later. Incorrect
poi
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit fae2ae2a900a5c7bb385fe4075f343e7e2d5daa2 upstream.
If a signal handler is executed on altstack and another signal comes,
we will end up with rt_sigreturn() on return from the sec
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Guennadi Liakhovetski
commit a7227a0faa117d0bc532aea546ae5ac5f89e8ed7 upstream.
dev_pm_qos_add_request() can return 0, 1, or a negative error code,
therefore the correct error test is "if (erro
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Kailang Yang
commit 7ff34ad80b7080fafaac8efa9ef0061708eddd51 upstream.
These are compatible with standard ALC269 parser.
Signed-off-by: Kailang Yang
Signed-off-by: Takashi Iwai
Signed-off-by
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Duncan Roe
commit 7110005e8d5c3cd418fc4b64f9f124f004422a9a upstream.
Signed-off-by: Duncan Roe
Signed-off-by: Takashi Iwai
Signed-off-by: Greg Kroah-Hartman
---
sound/pci/hda/patch_realtek
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Robert Richter
commit 1022623842cb72ee4d0dbf02f6937f38c92c3f41 upstream.
In 32 bit the stack address provided by kernel_stack_pointer() may
point to an invalid range causing NULL pointer access
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Fleming
commit 0f905a43ce955b638139bd84486194770a6a2c08 upstream.
Building for Athlon/Duron/K7 results in the following build error,
arch/x86/boot/compressed/eboot.o: In function `__const
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Boris Ostrovsky
commit 36c46ca4f322a7bf89aad5462a3a1f61713edce7 upstream.
Add valid patch size for family 16h processors.
[ hpa: promoting to urgent/stable since it is hw enabling and trivial
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Tilman Schmidt
commit c6fdd8e5d0c65bb8821dc6da26ee1a2ddd58b3cc upstream.
The delayed work function int_in_work() may call usb_reset_device()
and thus, indirectly, the driver's pre_reset method.
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Simon Wunderlich
commit b78a4932f5fb11fadf41e69c606a33fa6787574c upstream.
The check whether the IBSS is active and can be removed should be
performed before deinitializing the fields used for
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Bing Zhao
commit dd321acddc3be1371263b8c9e6c6f2af89f63d57 upstream.
When host_sleep_config command fails we should return error to
MMC core to indicate the failure for our device.
The misspell
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit 6d9359280753d2955f86d6411047516a9431eb51 upstream.
Sometimes, warnings about ioctls to partition happen often enough that they
form majority of the warnings in the kernel log an
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Bing Zhao
commit b1a47aa5e1e159e2cb06d7dfcc17ef5149b09299 upstream.
Reported by Tim Shepard:
I was seeing sporadic failures (wedgeups), and the majority of those
failures I saw printed the prin
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 5bc9ad774c063f6b41965e7314f2c26aa5e465a0 upstream.
Gcc 4.6.2 complains that:
drivers/leds/leds-lp5521.c: In function `lp5521_load_program':
drivers/leds/leds-lp5521.c:
On Fri, Nov 30, 2012 at 12:38 AM, Arend van Spriel wrote:
> So what is the rationale here. During mainlining our drivers we had to
> remove all uses of 'typedef struct foo foo_t;'. The Linux CodingStyle
> (chapter 5 Typedefs) is spending a number of lines explaining why.
>
> So is spinlock_t an ex
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Gavin Shan
commit feadf7c0a1a7c08c74bebb4a13b755f8c40e3bbc upstream.
The EEH core is talking with the PCI device driver to determine the
action (purely reset, or PCI device removal). During the
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jaehoon Chung
commit 5feb54a1ab91a237e247c013b8c4fb100ea347b1 upstream.
We can use up to four bus-clocks; but on module remove, we didn't
disable the fourth bus clock.
Signed-off-by: Jaehoon C
3.4-stable review patch. If anyone has any objections, please let me know.
--
commit 9d7d6e363b06934221b81a859d509844c97380df upstream.
read_persistent_clock uses a global variable, use a spinlock to
ensure non-atomic updates to the variable don't overlap and cause
time to move
On Fri, Nov 30, 2012 at 10:45:44AM -0800, Dmitry Torokhov wrote:
> However you snipped the rest of my reply: do we really need to renumber
> ioctls? There is no benefit for the driver as its ioctl handler does
> not parse the numbers into components.
I don't know if you need to renumber, I really
3.6-stable review patch. If anyone has any objections, please let me know.
--
From: Clemens Ladisch
commit e99ddfde6ae0dd2662bb40435696002b590e4057 upstream.
Commit 88a8516a2128 (ALSA: usbaudio: implement USB autosuspend) added
autosuspend code to all files making up the snd-u
On Fri, Nov 30, 2012 at 01:40:18PM -0500, David Miller wrote:
> From: "John W. Linville"
> Date: Fri, 30 Nov 2012 13:25:00 -0500
>
> > I have a couple of stragglers intended for 3.7...
> >
> > The iwlwifi patch fixes a bug in CCK basic rate calculations.
> >
> > The mac80211 patch removes an un
101 - 200 of 671 matches
Mail list logo
