Ma noted that dynamic-debug is silent about many query errors, so add
pr_err()s to explain those errors, and tweak a few others. Also parse
flags 1st, so that match-spec errs are slightly clearer.
To: Jason Baron
CC: Jianpeng Ma
CC: Joe Perches
CC: Greg KH
Signed-off-by: Jim Cromie
---
On Thu, 15 Nov 2012, Nithin Sujir wrote:
> > Would you mind submitting this for stable by following the procedure
> > described in Documentation/stable_kernel_rules.txt?
>
>
> Seems to have been taken into stable already.
>
On Wed, Nov 14, 2012 at 09:09:28PM +0530, Laxman Dewangan wrote:
> TPS80031/ TPS80032 Fully Integrated Power Management with Power
> Path and Battery Charger. The device provides five configurable
> step-down converters, 11 general purpose LDOs, USB OTG Module,
> ADC, RTC, 2 PWM, System Voltage
On Tue, 13 Nov 2012, Namhyung Kim wrote:
> From: Namhyung Kim
>
> Implement progress update function for GTK2 front end.
>
> Note that since it will be called before gtk main loop so that
> we should call gtk event loop handler directly.
>
> Cc: Pekka Enberg
> Signed-off-by: Namhyung Kim
>
Change the spare fuse base from a definition to a variable.
It provides flexibilty to read spare fuse on different chip.
Signed-off-by: Danny Huang
---
arch/arm/mach-tegra/fuse.c | 19 ---
arch/arm/mach-tegra/fuse.h | 2 ++
2 files changed, 14 insertions(+), 7 deletions(-)
Detect CPU and core process ID by checking speedo corner tables.
This can provide a more accurate process ID.
Signed-off-by: Danny Huang
---
arch/arm/mach-tegra/Makefile | 1 +
arch/arm/mach-tegra/fuse.c | 31 +++---
arch/arm/mach-tegra/fuse.h | 7 +++
This patch series adds speedo identification functionality for tegra
T20 and T30. It reads speedo value from fuse and chooses CPU and core
process ID by checking speedo corner tables.
V2:
* Split spare fuse related changes to a separate patch
* Keep original fuse init flow on an unknown chip
*
This patch adds speedo-based process identification support for T30.
Signed-off-by: Danny Huang
---
arch/arm/mach-tegra/Makefile | 1 +
arch/arm/mach-tegra/fuse.c | 11 +-
arch/arm/mach-tegra/fuse.h | 7 +
arch/arm/mach-tegra/tegra30_speedo.c | 292
On Thu, 15 Nov 2012, Namhyung Kim wrote:
> This is an RFC patchset to separate GTK GUI codes to a shared object,
> called libperf-gtk.so and use it with libdl. It's in an early-stage
> so probably has some rough edges, but I'd like to get some comments.
>
> For now, the libperf-gtk.so (I'm open
Since the task handoff notifier is isolated only to oprofile, it no
longer consists of a possible chain of notifiers. Thus, it's easy to
replace it with a simple linked list when enabled, which is anytime that
the notifier would have been registered.
Signed-off-by: David Rientjes
---
In the discussion surrounding 83dbbdbb3866 ("android, lowmemorykiller:
remove task handoff notifier"), I promised to isolate the task handoff
notifier to oprofile. The bug that was fixed in that commit occurred
because a task handoff notifier registered before oprofile was not
freeing the
On 11/14/2012 11:50 AM, Hugh Dickins wrote:
On Wed, 14 Nov 2012, Jaegeuk Hanse wrote:
On 11/07/2012 07:48 AM, Hugh Dickins wrote:
On Tue, 6 Nov 2012, Dave Jones wrote:
On Mon, Nov 05, 2012 at 05:32:41PM -0800, Hugh Dickins wrote:
> - /* We already confirmed swap, and
Hi David,
Thanks again for your inspirational comments!
On Wed, Nov 14, 2012 at 07:59:52PM -0800, David Rientjes wrote:
> > > I agree that eventfd is the way to go, but I'll also add that this
> > > feature
> > > seems to be implemented at a far too coarse of level. Memory, and hence
> > >
Dear Axel Lin,
On Thu, 15 Nov 2012 12:51:36 +0800, Axel Lin wrote:
> of_match_device() may return NULL.
>
> Signed-off-by: Axel Lin
Could you detail under what conditions of_match_device() may return
NULL in the specific case of this driver? This of_match_device() call
is using the same
From: Nick Cheng
Modify ARC-1214 IO behavior to make up for HW seldom malfunction.
Signed-off-by: Nick Cheng
---
patch5
Description: Binary data
On Wed, Nov 14, 2012 at 8:12 PM, Jeff Liu wrote:
> Hello,
>
> The problems have been fixed in this version as per Kees's comments for v3.
>
> Hi Kees,
> Would you please ACK this patch if you think it is ok except the strength
> of these various RNGs you are concerned?
>
>
> Changes:
>
>
On Wed, Nov 14, 2012 at 01:33:42PM -0800, Andrew Morton wrote:
> On Wed, 7 Nov 2012 17:00:52 +0200
> "Kirill A. Shutemov" wrote:
>
> > Andrew, here's updated huge zero page patchset.
>
> There is still a distinct lack of reviewed-by's and acked-by's on this
> patchset.
>
> On 13 Sep, Andrea
At Wed, 14 Nov 2012 20:10:47 -0800,
Greg Kroah-Hartman wrote:
>
> 3.6-stable review patch. If anyone has any objections, please let me know.
It turned out that this patch series for fixing USB-audio
disconnection races need two more commits. One is already in Linus
tree,
commit
From: Nick Cheng
Support MSI or MSI-X for whole series of RAID controllers. Meanwhile correct
the register access as iowrite32/ioread32
Signed-off-by: Nick Cheng
---
patch3
Description: Binary data
From: Nick Cheng
Support hibernation for whole series of RAID controllers
Signed-off-by: Nick Cheng
---
patch2
Description: Binary data
> -Original Message-
> From: David Rientjes [mailto:rient...@google.com]
> Sent: Wednesday, November 14, 2012 7:31 PM
> To: Nithin Sujir; Paul Gortmaker
> Cc: Denys Fedoryshchenko; Michael Chan; net...@vger.kernel.org; linux-
> ker...@vger.kernel.org
> Subject: Re: Latest 3.6.6 are not
Linus,
please pull sound fixes for v3.7-rc6 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git tags/sound-3.7
The topmost commit is 10e44239f67d0b6fb74006e61a7e883b8075247a
Sound fixes for 3.7-rc6
The only
On Thu, Nov 15, 2012 at 08:15:15AM +0100, Guennadi Liakhovetski wrote:
> parts are pretty simple - DCDC step-down, LDO. The first step-up DCDC
> isn't a problem either. It's the second step-up supply, that I'm having a
> problem with. It's output voltage can be regulated by using either a
>
Namjae Jeon writes:
> 1)If we consider the code for FAT and MSDOS to be same with respect to
> timing updates - there there is difference in code as mentioned below:
> a) For:vfat_rmdir()
> inode->i_mtime = inode->i_atime = CURRENT_TIME_SEC;
>For:msdos_rmdir()
>
Hi all,
News: this one will be the last release until next-20121126 (which should
be just be after -rc7, I guess - assuming that Linus does not release
v3.7 before then).
Changes since 20121114:
The v4l-dvb tree still had its build failure so I used the version from
next-20121026.
The wireless
Hi
I'm trying to implement a regulator driver for a PMIC [1], and so far I
don't see how it can be mapped to the present regulator API. Most its
parts are pretty simple - DCDC step-down, LDO. The first step-up DCDC
isn't a problem either. It's the second step-up supply, that I'm having a
On Thu, 2012-11-15 at 18:06 +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> lib/pSeries-reconfig-notifier-error-inject.c:4:34: fatal error:
> asm/pSeries_reconfig.h: No such file or directory
>
>
On Thu, Nov 15, 2012 at 08:56:17AM +0200, Terje Bergström wrote:
> On 14.11.2012 22:04, Thierry Reding wrote:
> > According to tegra20_clocks_data.c, the maximum clock frequency for
> > host1x is 166 MHz, so 216 is probably not a good idea. 150 MHz sounds
> > sensible, though.
> >
> > I was going
Thanks for the comments. See my response below.
> -Original Message-
> From: Bjorn Helgaas [mailto:bhelg...@google.com]
> Sent: Wednesday, November 14, 2012 4:51 PM
> To: Pandarathil, Vijaymohan R
> Cc: linux-kernel@vger.kernel.org; linux-...@vger.kernel.org;
> linasveps...@gmail.com;
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
lib/pSeries-reconfig-notifier-error-inject.c:4:34: fatal error:
asm/pSeries_reconfig.h: No such file or directory
Caused by commit f459d63e1689 ("powerpc+of: Remove the pSeries_reconfig.h
2012/11/12, OGAWA Hirofumi :
> OGAWA Hirofumi writes:
>
>> Namjae Jeon writes:
>>
> What was difference with XFS, FAT, and MSDOS?
>>> Okay, the description of patch was lacked, So I will resend patch with
>>> specifical test reseult with other filesystem.
BTW, I recall I checked
We eject the memory device even if it is in use. It is very dangerous,
and it will cause the kernel to be panicked.
CC: David Rientjes
CC: Jiang Liu
CC: Len Brown
CC: Benjamin Herrenschmidt
CC: Paul Mackerras
CC: Christoph Lameter
Cc: Minchan Kim
CC: Andrew Morton
CC: KOSAKI Motohiro
We allocate memory to store acpi_memory_info, so we should free it before
freeing mem_device.
CC: David Rientjes
CC: Jiang Liu
CC: Len Brown
CC: Benjamin Herrenschmidt
CC: Paul Mackerras
CC: Christoph Lameter
Cc: Minchan Kim
CC: Andrew Morton
CC: KOSAKI Motohiro
CC: Yasuaki Ishimatsu
If the memory device is hotplugged before the driver is loaded, the user
cannot see this device under the directory /sys/bus/acpi/devices/, and the
user cannot bind it by hand after the driver is loaded. This patch
introduces a new feature to bind such device when the driver is being
loaded.
CC:
The memory device can be removed by 2 ways:
1. send eject request by SCI
2. echo 1 >/sys/bus/pci/devices/PNP0C80:XX/eject
We handle the 1st case in the module acpi_memhotplug, and handle
the 2nd case in ACPI eject notification. This 2 events may happen
at the same time, so we may touch
From: Yasuaki Ishimatsu
The memory device can be removed by 2 ways:
1. send eject request by SCI
2. echo 1 >/sys/bus/pci/devices/PNP0C80:XX/eject
In the 1st case, acpi_memory_disable_device() will be called.
In the 2nd case, acpi_memory_device_remove() will be called.
The memory device can be removed by 2 ways:
1. send eject request by SCI
2. echo 1 >/sys/bus/pci/devices/PNP0C80:XX/eject
In the 1st case, acpi_memory_disable_device() will be called.
In the 2nd case, acpi_memory_device_remove() will be called.
acpi_memory_device_remove() will also be called when
If acpi_memory_enable_device() fails, acpi_memory_enable_device() will
return a non-zero value, which means we fail to bind the memory device to
this driver. So we should free memory device before
acpi_memory_device_add() returns.
CC: David Rientjes
CC: Jiang Liu
CC: Len Brown
CC: Benjamin
We had introduced acpi_hotmem_initialized to avoid strange add_memory fail
message. But the memory device may not be used by the kernel, and the
device should be bound when the driver is being loaded. Remove
acpi_hotmem_initialized to allow that the device can be bound when the
driver is being
On 14.11.2012 22:04, Thierry Reding wrote:
> According to tegra20_clocks_data.c, the maximum clock frequency for
> host1x is 166 MHz, so 216 is probably not a good idea. 150 MHz sounds
> sensible, though.
>
> I was going to send a new version of the patch set tonight, but I'll
> wait until I can
* Oleg Nesterov [2012-11-14 19:49:53]:
> This was always racy, but 268720903f87e0b84b161626c4447b81671b5d18
> "uprobes: Rework register_for_each_vma() to make it O(n)" should be
> blamed anyway, it made everything worse and I didn't notice.
>
> register/unregister call build_map_info() and then
On Thu, Nov 15, 2012 at 10:30:11AM +0900, Jingoo Han wrote:
> On Friday, November 09, 2012 11:05 PM Thierry Reding wrote
> >
> > This function finds the struct backlight_device for a given device tree
> > node. A dummy function is provided so that it safely compiles out if OF
> > support is
At 11/15/2012 03:52 AM, Andrew Morton Wrote:
> On Fri, 02 Nov 2012 15:41:55 +0800
> Wen Congyang wrote:
>
>> At 11/02/2012 05:36 AM, David Rientjes Wrote:
>>> On Thu, 1 Nov 2012, Wen Congyang wrote:
>>>
> This doesn't describe why we need the new node state, unfortunately. It
1.
On Thu, Nov 15, 2012 at 02:56:45AM +, Alexandra Chin wrote:
> Hi Dmitry,
>
> > > As I know, currently there is no synaptics RMI4 touchscreen driver in the
> > > main tree. In order to support our customers effectively, is it able to
> > > merge
> > > staging ste_rmi4 driver into the main
On 13 November 2012 04:46, Linus Walleij wrote:
> On Mon, Nov 12, 2012 at 7:07 AM, Zhang Rui wrote:
>> On Fri, 2012-11-09 at 19:29 +0800, hongbo.zhang wrote:
>>> From: "hongbo.zhang"
>>>
>>> This patch adds device tree properties for ST-Ericsson DB8500 thermal
>>> driver,
>>> also adds the
devm_* functions are device managed and make the code and error
handling a bit simpler.
Cc: Jassi Brar
Signed-off-by: Sachin Kamat
---
drivers/dma/pl330.c | 37 ++---
1 files changed, 10 insertions(+), 27 deletions(-)
diff --git a/drivers/dma/pl330.c
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in mm/mprotect.c
between commit a9463d90124a ("mm: Count the number of pages affected in
change_protection()") from the tip tree and commit "thp: change
split_huge_page_pmd() interface" from the akpm tree.
I fixed it up (see
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in
mm/memcontrol.c between commit 2ef37d3fe474 ("memcg: Simplify
mem_cgroup_force_empty_list error handling") from the cgroup tree and
commit 4bfe8322f427 ("memcg: fix hotplugged memory zone oops") from the
akpm-current
Now, 'perf kvm stat' is only supported on x86, let its code depend
on ARCH_X86 to fix building it on other architectures
Signed-off-by: Xiao Guangrong
---
tools/perf/arch/x86/Makefile |2 ++
tools/perf/builtin-kvm.c |4
2 files changed, 6 insertions(+), 0 deletions(-)
diff
Then, let it only be used in 'perf kvm stat'
Signed-off-by: Xiao Guangrong
---
tools/perf/builtin-kvm.c | 111 +-
1 files changed, 60 insertions(+), 51 deletions(-)
diff --git a/tools/perf/builtin-kvm.c b/tools/perf/builtin-kvm.c
index
On Tuesday 13 November 2012 04:07 PM, Arnd Bergmann wrote:
> On Tuesday 13 November 2012, Gilad Ben-Yossef wrote:
>> So, I completely agree about not adding more deprecated system call or
>> ABIs (thinking about the ptrace regset issues in another patch in the
>> same patchset), but on the other
"J. Bruce Fields" writes:
> On Wed, Nov 14, 2012 at 09:51:33PM +, Myklebust, Trond wrote:
>> On Wed, 2012-11-14 at 16:42 -0500, J. Bruce Fields wrote:
>> > Simo's patches use them for upcalls to svcgssd. Those will always be
>> > done from server threads.
>>
>> Any reason why you can't set
Hi all,
Today's linux-next merge of the powerpc tree got a conflict in
arch/powerpc/kernel/entry_64.S between commits 40792104b255 ("powerpc:
don't mess with r2 in copy_thread() and friends") and 53b50f9483cc
("powerpc: take dereferencing to ret_from_kernel_thread()") from the
signal tree and
On Wed, Nov 14, 2012 at 09:09:29PM +0530, Laxman Dewangan wrote:
> Pefix "TPS80031" is added on all defines of tps80031 header
> to avoid conflict with other header definitions.
> Update the regualtor driver of tps80031 to use the same name.
Appiled, thanks.
signature.asc
Description: Digital
On Thu, Nov 01, 2012 at 01:57:56PM +0530, Ashish Jangam wrote:
> This is the Regulator patch for the DA9055 PMIC and has got dependency on
> the DA9055 MFD core.
Applied, thanks.
signature.asc
Description: Digital signature
Hi all,
Today's linux-next merge of the arm-soc tree got a conflict in
arch/arm/plat-omap/i2c.c between commit 49839dc93970 ("Revert "ARM: OMAP:
convert I2C driver to PM QoS for MPU latency constraints"") from the
i2c-embedded tree and various commits from the arm-soc tree.
I used the version
On Tue, Nov 13, 2012 at 03:38:18PM +0200, Pantelis Antoniou wrote:
> Hi Grant,
>
> On Nov 13, 2012, at 2:24 PM, Grant Likely wrote:
> > On Tue, Nov 13, 2012 at 8:09 AM, Pantelis Antoniou
[snip]
> My intention wasn't never to make overlays overly portable. My intention
> was to make them in a way
On Thu, Oct 18, 2012 at 07:36:09PM +0530, Laxman Dewangan wrote:
> Moving regulator node parsing to regulator driver in place
> of parsing it on mfd driver.
Applied, thanks.
signature.asc
Description: Digital signature
Vivek Goyal writes:
> On Thu, Nov 08, 2012 at 01:03:17PM -0800, Eric W. Biederman wrote:
>> Vivek Goyal writes:
>>
>> > On Thu, Nov 08, 2012 at 02:40:50PM -0500, Vivek Goyal wrote:
>> >> On Tue, Nov 06, 2012 at 03:51:59PM -0800, Eric W. Biederman wrote:
>> >>
>> >> [..]
>> >>
>> >> Thnking
of_match_device() may return NULL.
Signed-off-by: Axel Lin
---
This resend CC Jean-Christophe.
drivers/pinctrl/pinctrl-at91.c | 17 +
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/drivers/pinctrl/pinctrl-at91.c b/drivers/pinctrl/pinctrl-at91.c
index
of_match_device() may return NULL.
Signed-off-by: Axel Lin
---
drivers/pinctrl/pinctrl-nomadik.c | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/drivers/pinctrl/pinctrl-nomadik.c
b/drivers/pinctrl/pinctrl-nomadik.c
index 238060e..40bd1b3 100644
---
of_match_device() may return NULL.
Signed-off-by: Axel Lin
---
drivers/pinctrl/mvebu/pinctrl-kirkwood.c |7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/pinctrl/mvebu/pinctrl-kirkwood.c
b/drivers/pinctrl/mvebu/pinctrl-kirkwood.c
index 9a74ef6..fe885ca
of_match_device() may return NULL.
Signed-off-by: Axel Lin
---
drivers/pinctrl/pinctrl-at91.c | 17 +
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/drivers/pinctrl/pinctrl-at91.c b/drivers/pinctrl/pinctrl-at91.c
index 8490a55..32006c8 100644
---
of_match_device() may return NULL.
Signed-off-by: Axel Lin
---
drivers/pinctrl/mvebu/pinctrl-dove.c |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/pinctrl/mvebu/pinctrl-dove.c
b/drivers/pinctrl/mvebu/pinctrl-dove.c
index ffe74b2..a8b9b42 100644
---
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Stanislaw Gruszka
commit bf7e1abe434ba9e22e8dc04a4cba4ab504b788b8 upstream.
Some hardware has correct (!= 0xff) value of tssi_bounds[4] in the
EEPROM, but step is equal to 0xff. This results
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit c4a9fafc77a5318f5ed26c509bbcddf03e18c201 upstream.
No driver initializes chan->max_antenna_gain to something sensible, and
the only place where it is being used right now
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 7dd111e8ee10cc6816669eabcad3334447673236 upstream.
The mesh header can have address extension by a 4th
or a 5th and 6th address, but never both. Drop such
frames in 802.11
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Javier Cardona
commit f7fbf70ee9db6da6033ae50d100e017ac1f26555 upstream.
Per IEEE Std. 802.11-2012, Sec 8.2.4.4.1, the sequence Control field is
not present in control frames. We noticed this
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Scott Mayhew
commit acce94e68a0f346115fd41cdc298197d2d5a59ad upstream.
In very busy v3 environment, rpc.mountd can respond to the NULL
procedure but not the MNT procedure in a timely manner
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit 2b1bc308f492589f7d49012ed24561534ea2be8c upstream.
If the state recovery machinery is triggered by the call to
nfs4_async_handle_error() then we can deadlock.
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: "J. Bruce Fields"
commit a007c4c3e943ecc054a806c259d95420a188754b upstream.
I don't think there's a practical difference for the range of values
these interfaces should see, but it would be
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
[Fixed upstream as part of 0b728e1911c, but that's a much larger patch,
this is only the nfs portion backported as needed.]
Fix the following Oops in 3.5.1:
BUG: unable to
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Egbert Eich
commit 83325d072185899b706de2956170b246585aaec9 upstream.
An uninitialized variable led to broken load detection.
Signed-off-by: Egbert Eich
Signed-off-by: Alex Deucher
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 978520b75f0a1ce82b17e1e8186417250de6d545 upstream.
Close some races at disconnection of a USB audio device by adding the
chip->shutdown_mutex and chip->shutdown check at
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 34f3c89fda4fba9fe689db22253ca8db2f5e6386 upstream.
Replace mutex with rwsem for codec->shutdown protection so that
concurrent accesses are allowed.
Also add the protection
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 888ea7d5ac6815ba16b3b3a20f665a92c7af6724 upstream.
Similar like the previous commit, cover with chip->shutdown_rwsem
and chip->shutdown checks.
Reported-by: Matthieu
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit a0830dbd4e42b38aefdf3fb61ba5019a1a99ea85 upstream.
For more strict protection for wild disconnections, a refcount is
introduced to the card instance, and let it up/down
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 0914f7961babbf28aaa2f19b453951fb4841c03f upstream.
When disconnect callback is called, each component should wake up
sleepers and check card->shutdown flag for avoiding the
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit a3374c42aa5f7237e87ff3b0622018636b0c847e ]
tcp_ioctl() tries to take into account if tcp socket received a FIN
to report correct number bytes in receive queue.
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Li RongQing
[ Upstream commit 14edd87dc67311556f1254a8f29cf4dd6cb5b7d1 ]
Commit a02e4b7dae4551(Demark default hoplimit as zero) only changes the
hoplimit checking condition and default value
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Hemant Kumar
[ Upstream commit 39707c2a3ba5011038b363f84d37c8a98d2d9db1 ]
Driver anchors the tx urbs and defers the urb submission if
a transmit request comes when the interface is suspended.
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jesper Dangaard Brouer
[ Upstream commit 8f363b77ee4fbf7c3bbcf5ec2c5ca482d396d664 ]
Reading TCP stats when using TCP Illinois congestion control algorithm
can cause a divide by zero kernel
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Tom Parkin
[ Upstream commit 789336360e0a2aeb9750c16ab704a02cbe035e9e ]
When creating an L2TPv3 Ethernet session, if register_netdev() should fail for
any reason (for example, automatic
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Zijie Pan
[ Upstream commit f6e80abeab928b7c47cc1fbf53df13b4398a2bec ]
Bug introduced by commit edfee0339e681a784ebacec7e8c2dc97dc6d2839
(sctp: check src addr when processing SACK to update
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Vetter
commit 81014b9d0b55fb0b48f26cd2a943359750d532db upstream.
At least the worst offenders:
- SDVO specifies that the encoder should compute the ecc. Testing also
shows that we
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Hannes Frederic Sowa
[ Upstream commit 60713a0ca7fd6651b951cc1b4dbd528d1fc0281b ]
As documented in RFC4861 (Neighbor Discovery for IP version 6) 7.2.6.,
unsolicited neighbour advertisements
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 6d772ac5578f711d1ce7b03535d1c95bffb21dff ]
On some suspend/resume operations involving wimax device, we have
noticed some intermittent memory corruptions in
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jean Delvare
commit 3300fb4f88688029fff8dfb9ec0734f6e4cba3e7 upstream.
Don't assume bank 0 is selected at device probe time. This may not be
the case. Force bank selection at first register
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 9b0573c07f278e9888c352aa9724035c75784ea0 upstream.
Fix races at PCM disconnection:
- while a PCM device is being opened or closed
- while the PCM state is being changed
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Antonio Quartulli
commit badecb001a310408d3473b1fc2ed5aefd0bc92a9 upstream.
The 'ssid' field of the cfg80211_ibss_params is a u8 pointer and
its length is likely to be less than
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
commit 97a54868262da1629a3e65121e65b8e8c4419d9f upstream.
Since commit c7f404b ('vfs: new superblock methods to override
/proc/*/mount{s,info}'), nfs_path() is used to generate
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 4a4f1a5808c8bb0b72a4f6e5904c53fb8c9cd966 upstream.
Due to pskb_may_pull() checking the skb length, all
non-management frames are checked on input whether
their 802.11
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Roland Dreier
commit 0d0f9dfb31e0a6c92063e235417b42df185b3275 upstream.
If the call to core_dev_release_virtual_lun0() fails, then nothing
sets ret to anything other than 0, so even though
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit 8c6e30936a7893a85f6222084f0f26aceb81137a upstream.
bf->bf_next is only while buffers are chained as part of an A-MPDU
in the tx queue. When a tid queue is flushed (e.g. on
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Chinner
commit 6ce377afd1755eae5c93410ca9a1121dfead7b87 upstream.
Commit 4439647 ("xfs: reset buffer pointers before freeing them") in
3.0-rc1 introduced a regression when recovering log
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Gleixner
commit 59fa6245192159ab5e1e17b8e31f15afa9cff4bf upstream.
Siddhesh analyzed a failure in the take over of pi futexes in case the
owner died and provided a workaround.
See:
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
Fix warning about unused variable introduced by commit e681b66f2e19fa
("USB: mos7840: remove invalid disconnect handling") upstream.
A subsequent fix which removed the disconnect
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Roland Dreier
commit 3e7abe2556b583e87dabda3e0e6178a67b20d06f upstream.
When unbinding a device so that I could pass it through to a KVM VM, I
got the lockdep report below. It looks like a
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Hellstrom
commit 95e8f6a21996c4cc2c4574b231c6e858b749dce3 upstream.
The device would not reset properly when resuming from hibernation.
Signed-off-by: Thomas Hellstrom
Reviewed-by:
3.6-stable review patch. If anyone has any objections, please let me know.
--
From: Konrad Rzeszutek Wilk
commit 95a7d76897c1e7243d4137037c66d15cbf2cce76 upstream.
As Mukesh explained it, the MMUEXT_TLB_FLUSH_ALL allows the
hypervisor to do a TLB flush on all active vCPUs. If
1 - 100 of 1642 matches
Mail list logo
