On Fri, 14 Sep 2012, Wen Congyang wrote:
>
> Hmm, if we don't update lruvec_zone(lruvec) when a node is onlined,
> lruver_zone(lruvec) contains a invalid pointer, so we should check
> all place that accesses lruvec_zone(lruvec). We store zone in lruvec
> but we can't access it. And we can't avoid
On 09/17/2012 03:55 AM, Nicolas Pitre wrote:
On Sun, 16 Sep 2012, Jason Cooper wrote:
On Sun, Sep 16, 2012 at 09:46:52AM +0200, Andrew Lunn wrote:
+++ b/Documentation/devicetree/bindings/pinctrl/marvell,kirkwood-pinctrl.txt
@@ -0,0 +1,279 @@
+* Marvell Kirkwood SoC pinctrl driver for mpp
+
+Ple
On Thu, Sep 13, 2012 at 04:37:54PM +0300, Peter Ujfalusi wrote:
> Change the parameter list of device_prep_dma_cyclic() so the DMA drivers
> can receive the no_wakeup request coming from client drivers.
> This feature can be used during audio operation to disable all audio
> related interrupts.
>
I would suggest to remove the Roccat devices from generic drivers blacklist.
Some Distros tend to have kernels without the special modules compiled, which
prevents users of these devices to work with live images or installers.
The Roccat devices work flawlessly with generic drivers (except the ol
On Fri, Sep 07, 2012 at 10:29:10PM -0700, Anton Vorontsov wrote:
> On Fri, Sep 07, 2012 at 11:29:36AM -0700, Bryan Freed wrote:
> > When called with a non-zero of_node, fill out a new ramoops_platform_data
> > with data from the specified Flattened Device Tree node.
> > Update ramoops documentation
On Fri, Sep 14, 2012 at 13:50:57, Jonathan Cameron wrote:
> On 14/09/12 07:00, Patil, Rachna wrote:
> > On Thu, Sep 13, 2012 at 17:43:30, Jonathan Cameron wrote:
> >> On 13/09/12 11:40, Patil, Rachna wrote:
> >>> This patch adds support for TI's ADC driver.
> >>> This is a multifunctional device.
>
Hi all,
On Sat, Sep 01, 2012 at 10:43:35PM -0700, Anton Vorontsov wrote:
> This patch set implements a userland-side API for generic deferrable
> timers, per linux/timer.h:
>
> * A deferrable timer will work normally when the system is busy, but
> * will not cause a CPU to come out of idle just
Hi,
On Mon, Sep 17, 2012 at 6:50 AM, Chen Peter-B29397 wrote:
>
>>
>> The PHY framework provides a set of API's for the PHY drivers to
>> create/remove a PHY and the PHY users to obtain a reference to the PHY
>> using or without using phandle. If the PHY users has to obtain a
>> reference to
>> t
On Mon, Sep 17, 2012 at 9:57 AM, Inderpal Singh
wrote:
> Since 0 is not considered as error at dmaengine level, return ENOMEM
> from pl330_alloc_chan_resources in case of failure.
>
> Signed-off-by: Inderpal Singh
Acked-by: Jassi Brar
> ---
> drivers/dma/pl330.c |2 +-
> 1 file changed,
At 09/14/2012 09:36 AM, Hugh Dickins Wrote:
> On Thu, 13 Sep 2012, Johannes Weiner wrote:
>> On Thu, Sep 13, 2012 at 03:14:28PM +0800, Wen Congyang wrote:
>>> root_mem_cgroup->info.nodeinfo is initialized when the system boots.
>>> But NODE_DATA(nid) is null if the node is not onlined, so
>>> root_
Remove redundant check in is_volatile_reg().
Signed-off-by: Venu Byravarasu
---
drivers/mfd/tps65090.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/mfd/tps65090.c b/drivers/mfd/tps65090.c
index 50fd87c..074ae32 100644
--- a/drivers/mfd/tps65090.c
+++ b/driver
From: "John W. Linville"
Date: Fri, 14 Sep 2012 13:46:55 -0400
> Arend van Spriel sends a simple thinko fix to correct a constant,
> preventing the setting of an invalid power level.
>
> Colin Ian King gives us a simple allocation failure check to avoid a
> NULL pointer dereference.
>
> Felix F
When either of __alloc_from_contiguous or __alloc_remap_buffer fails
to provide a valid pointer, allocated memory is freed up and an error
is returned. 'pages' was however not freed before returning error.
Cc: Arnd Bergmann
Cc: Marek Szyprowski
Signed-off-by: Sachin Kamat
---
arch/arm/mm/dma-m
> On Fri, Sep 07, 2012 at 03:22:09PM +0200, Thierry Reding wrote:
> > On Mon, Sep 03, 2012 at 01:28:44PM +0200, Arun MURTHY wrote:
> > > > On Sun, Sep 2, 2012 at 12:30 PM, Thierry Reding
> > > > wrote:
> > > >
> > > > > This commit moves the driver to drivers/pwm and converts it to
> > > > > the n
Hi Dave,
Today's linux-next merge of the drm tree got a conflict in
drivers/gpu/drm/i915/i915_dma.c between commit 99d0b1db6ccd ("drm/i915:
initialize dpio_lock spin lock") from Linus' tree and commit c6a828d3269a
("drm/i915: move all rps state into dev_priv->rps") from the drm tree.
I fixed it u
Since 0 is not considered as error at dmaengine level, return ENOMEM
from pl330_alloc_chan_resources in case of failure.
Signed-off-by: Inderpal Singh
---
drivers/dma/pl330.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/pl330.c b/drivers/dma/pl330.c
index e4
On Thu, Sep 13, 2012 at 4:22 PM, Haojian Zhuang
wrote:
> Remove the register offset definition. All these register offset
> are transfered as IORESOURCE_REG resources.
>
> Signed-off-by: Haojian Zhuang
> ---
> drivers/mfd/max8925-core.c | 31 ++---
> drivers/video/backlight/m
Signed-off-by: Haojian Zhuang
---
arch/arm/boot/dts/pxa910-dkb.dts | 137 ++
arch/arm/boot/dts/pxa910.dtsi|4 ++
2 files changed, 141 insertions(+)
diff --git a/arch/arm/boot/dts/pxa910-dkb.dts b/arch/arm/boot/dts/pxa910-dkb.dts
index e92be5a..595492a
The initilization of GPADC is moved from core driver to touch driver
with DT support.
Signed-off-by: Haojian Zhuang
---
drivers/input/touchscreen/88pm860x-ts.c | 91 +--
drivers/mfd/88pm860x-core.c | 51 -
2 files changed, 85 insertions
Signed-off-by: Haojian Zhuang
---
drivers/input/touchscreen/88pm860x-ts.c | 46 +++
drivers/leds/leds-88pm860x.c| 33 +++-
drivers/mfd/88pm860x-core.c | 62 ++-
drivers/regulator/88pm8607.c| 35
Use irqdomain and allocating interrupts. It's necessary for supporting
DT mode.
Signed-off-by: Haojian Zhuang
---
drivers/mfd/88pm860x-core.c | 65 +--
1 file changed, 38 insertions(+), 27 deletions(-)
diff --git a/drivers/mfd/88pm860x-core.c b/drivers/
Move probe() and other functions from 88pm860x-i2c.c to 88pm860x-core.c.
Since it could benefit to handle DT information.
Signed-off-by: Haojian Zhuang
---
drivers/mfd/88pm860x-core.c | 162 +-
drivers/mfd/88pm860x-i2c.c | 160
From: Haojian Zhuang
Since PREG regulator is the only one regulator in 88PM8606, and other
regulators are in 88PM8607. Checking resource as identifying regulator
is not a good way. We can use NULL resource to indentify PREG regulator.
Signed-off-by: Haojian Zhuang
---
drivers/mfd/88pm860x-core
From: "Jett.Zhou"
Pre-regulator of 88pm8606 is mainly for support charging based on vbus,
it needs to be enabled for charging battery, and will be disabled in
some exception condition like over-temp.
Add the pre-regulator support for 88pm860x regulator driver.
Signed-off-by: Jett.Zhou
Acked-by:
Remove array in parent's platform data. Use struct regulator_init_data
as regulator device's platform data directly. So a lot of pdata are
added into parent's platform data. And voltage out register offset
is used as IORESOURCE_REG to distinguish different regualtor devices.
Signed-off-by: Haojian
Remove the register offset definition. All these register offset
are transfered as IORESOURCE_REG resources.
Signed-off-by: Haojian Zhuang
---
drivers/mfd/max8925-core.c | 31 ++---
drivers/video/backlight/max8925_bl.c | 79 ++
2 files change
1. Updates the patch of max8925 of building issue.
2. Include Jett's PREG regulator patch.
3. Support DT in 88pm860x.
--
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 http://vger.kernel.org/majo
Hi,
On Fri, 14 Sep 2012 11:14:13 +0800, liang xie wrote:
> memory leak fix while calling system_path
>
> Since v1: Remove an unnecessary null pointer check per Felipe's comments
> Since v2: Make system_path&perf_exec_path always return dynamically
> allocated string
>
> Signed-off-by: xieliang
>
Hello Lars,
Thanks for the review.All of you comments are valid but
i just have a small question w.r.t one of your comments.
Inline below.
On Sun, Sep 16, 2012 at 9:11 PM, Lars-Peter Clausen wrote:
> On 09/16/2012 09:14 AM, anish kumar wrote:
>> From: anish kumar
>>
>> In last version:
>> Addre
On Fri, 2012-09-14 at 12:18 +0100, Russell King - ARM Linux wrote:
> I'm not saying take the slave_id out of the map. I'm saying, let the
> DMA engine driver itself figure out what dma_chan to return.
But wont that assume the dma controller knows which channel to allocate.
And how would it know t
Hi Nicholas,
After merging the target-updates tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/target/target_core_transport.c: In function
'transport_get_sense_buffer':
drivers/target/target_core_transport.c:582:22: error: 'struct
target_core_fabric_ops' has no mem
On Sun, Sep 16, 2012 at 10:30 AM, Xiaodong Xu wrote:
> Hi All,
>
> I found a bug in kernel PPPOE driver.
> When PPPOE is running over a virtual ethernet interface (e.g., a
> bonding interface) and the user tries to delete the interface in case
> the PPPOE state is ZOMBIE, the kernel will loop infi
Hi Nicholas,
Today's linux-next merge of the target-updates tree got a conflict in
drivers/target/target_core_transport.c between commit 6138ed2ab879
("target: move transport_get_sense_data") from Linus' tree and commit
867c8e7dae31 ("target: Simplify fabric sense data length handling") from
the t
On Mon, Sep 10, 2012 at 06:20:01PM -0400, Mark Salter wrote:
> C6X works fine with these patches to switch over to generic code.
>
>
> Mark Salter (2):
> c6x: implement ret_from_kernel_execve() and switch to generic
> kernel_execve()
> c6x: switch to generic sys_execve()
>
> arch/c6x/in
On Fri, 2012-09-14 at 15:05 +0300, Peter Ujfalusi wrote:
> Hello,
dmaengine parts look good to me. How do you want to get this merged,
dmaengine or ASoC tree?
>
> Changes since v2:
> - As it has been discussed the no_wakeup parameter has been replaced with
> flags
> for the dmaengine APIs
>
>
On Fri, 2012-09-14 at 15:05 +0300, Peter Ujfalusi wrote:
> - /* FIXME: not supported by platform private API */
> - return -EINVAL;
> + /* Pause/Resume only allowed with cyclic mode */
> + if (!c->cyclic)
> + return -EINVAL;
This is not a dma restriction right
Hi James,
Today's linux-next merge of the scsi tree got a conflict in
drivers/scsi/qla2xxx/qla_nx.c between commit 100924388407 ("[SCSI]
qla4xxx: Use PCI Express Capability accessors") from the pci tree and
commit 8fbb85e5f4c0 ("[SCSI] qla2xxx: Wrong PCIe(2.5Gb/s x8) speed in the
kerenel message f
Jan Engelhardt wrote:
On Thursday 2012-09-06 21:37, Lucas De Marchi wrote:
kmod 10 is out:
ftp://ftp.kernel.org/pub/linux/utils/kernel/kmod/kmod-10.tar.xz
ftp://ftp.kernel.org/pub/linux/utils/kernel/kmod/kmod-10.tar.sign
make check fails here with glibc-2.15, gcc-4.7, x86_64,
due to what se
On Fri, 2012-09-14 at 18:23 +0200, Davide Ciminaghi wrote:
> From: Alessandro Rubini
>
> This driver would not compile if ARM_AMBA is selected under x86,
> because "CS" and "DS" are already defined there. But AMBA
> is used in the x86 world by a PCI-to-AMBA bridge, to be submitted.
>
> The patc
On Sun, Sep 16, 2012 at 11:02 AM, Yinghai Lu wrote:
> On Sun, Sep 16, 2012 at 9:49 AM, Yinghai Lu wrote:
>> On Sun, Sep 16, 2012 at 7:09 AM, Jiang Liu wrote:
>>> @@ -160,10 +160,13 @@ static int acpi_bind_one(struct device *dev,
>>> acpi_handle handle)
>>> }
>>> dev->archdata.ac
On Sat, Sep 15, 2012 at 4:27 PM, Yinghai Lu wrote:
> On Fri, Sep 14, 2012 at 8:05 PM, Jiang Liu wrote:
>> From: Jiang Liu
>>
>> Now ACPI devices are created before/destroyed after corresponding PCI
>> devices, and acpi_platform_notify/acpi_platform_notify_remove will
>> update PCI<->ACPI bindin
try_to_grab_pending() leave LINKED tagalong in delayed queue when
it deletes a work. This behavior will cause future
cwq_activate_first_delayed() increase the ->nr_active wrongly,
and may cause the whole cwq frozen.
example:
state: cwq->max_active = 1, cwq->nr_active = 1
one work in cwq-
On Thursday 2012-09-06 21:37, Lucas De Marchi wrote:
>
>kmod 10 is out:
>
>ftp://ftp.kernel.org/pub/linux/utils/kernel/kmod/kmod-10.tar.xz
>ftp://ftp.kernel.org/pub/linux/utils/kernel/kmod/kmod-10.tar.sign
make check fails here with glibc-2.15, gcc-4.7, x86_64,
due to what seems to be duplicated
On 09/14/2012 11:02 AM, Michael Wang wrote:
> On 09/13/2012 06:04 PM, Peter Zijlstra wrote:
>> On Wed, 2012-08-22 at 10:40 +0800, Michael Wang wrote:
>>> From: Michael Wang
>>>
>>> Fengguang Wu has reported the bug:
>>>
>>> [0.043953] BUG: scheduling while atomic: swapper/0/1/0x1002
>>> [
On Sun, Sep 16, 2012 at 06:52:51PM -0600, Shuah Khan wrote:
> +void debug_dma_dump_map_errors(struct device *dev, int all)
> +{
> + if (all) {
> + dev_info(dev,
> + "DMA-API: DMA map error summary:\n"
> + "DMA map errors returned = %d\n"
> +
On Sun, 16 Sep 2012, Jason Cooper wrote:
> On Sun, Sep 16, 2012 at 09:46:52AM +0200, Andrew Lunn wrote:
> > > +++
> > > b/Documentation/devicetree/bindings/pinctrl/marvell,kirkwood-pinctrl.txt
> > > @@ -0,0 +1,279 @@
> > > +* Marvell Kirkwood SoC pinctrl driver for mpp
> > > +
> > > +Please refer
From: "Mathieu J. Poirier"
This patch adds keyreset functionality to the sysrq driver. It
allows certain button/key combinations to be used in order to
trigger device resets.
The first time the key-combo is detected a work function that syncs
the filesystems is scheduled and the kernel rebooted.
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit 92fc7a8b0f20bdb243c706daf42658e8e0cd2ef0 upstream.
This patch (as1604) adds a CONFIG_INTF_STRINGS quirk for the Joss
infrared touchboard device. The device doesn't like to be
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit e994defb7b6813ba6fa7a2a36e86d2455ad1dc35 upstream.
Use the *_light() versions that properly avoid doing the file user count
updates when they are unnecessary.
Signed-off-
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit 26fe45a0a76f165425f332a5aaa298f149f9db22 upstream.
Selecting ATOM_PPLL_INVALID should be equivalent as the
DCPLL or PPLL0 are already programmed for the DISPCLK, but
the pre
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Mel Gorman
commit bba3d8c3b3c0f2123be5bc687d1cddc13437c923 upstream.
The following build error occured during a parisc build with
swap-over-NFS patches applied.
net/core/sock.c:274:36: error:
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit ecd67955fd4c8e66e4df312098989d5fa7da624c upstream.
No functional change, but re-order the cases so they
evaluate properly due to the way the DCE macros work.
Noticed by kal
Hi Catalin,
After merging the arm64 tree, today's linux-next build ()
failed like this:
arch/powerpc/kernel/sys_ppc32.c:146:17: error: conflicting types for
'compat_sys_sendfile'
include/linux/compat.h:593:16: note: previous declaration of
'compat_sys_sendfile' was here
arch/powerpc/kernel/sys_
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: David Brown
commit 70b0476a2394de4f4e32e0b67288d80ff71ca963 upstream.
'make dtbs' in a clean tree will try running the dtc before actually
building it. Make these rules depend upon the scripts
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Xinyu Chen
commit 9ec1882df244c4ee1baa692676fef5e8b0f5487d upstream.
The console feature's write routing is unsafe on SMP with
the startup/shutdown call.
There could be several consumers of th
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit 985f61f7ee647ad570c05eab0b74915da2ac8e19 upstream.
For DP we can use the same PPLL for all active DP
encoders. Take advantage of that to prevent cases
where we may end up s
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit 55815f70147dcfa3ead5738fd56d3574e2e3c1c2 upstream.
We already use them for openat() and friends, but fstat() also wants to
be able to use O_PATH file descriptors. This sh
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Bjørn Mork
commit f08dea734844aa42ec57c229b0b73b3d7d21f810 upstream.
The Microchip vid:pid 04d8:000a is used for their CDC ACM
demo firmware application. This is a device with a single
functi
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Guenter Roeck
commit 73d7c119255615a26070f9d6cdb722a166a29015 upstream.
twl4030_madc_conversion uses do_avg and type structure elements of
twl4030_madc_request. Initialize structure to avoid ra
3.2-stable review patch. If anyone has any objections, please let me know.
Is this useful for 3.2 or does it depend on any other later changes?
(All I know is that it builds cleanly.)
--
From: Dave Airlie
commit 5e1782d224c79b26ab7d5c31e3f87657000714fb upstream.
Testing and w
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Torokhov
commit 7b125b94ca16b7e618c6241cb02c4c8060cea5e3 upstream.
They all define their chassis type as "Other" and therefore are not
categorized as "laptops" by the driver, which tries
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Matteo Frigo
commit 3737e2be505d872bf2b3c1cd4151b2d2b413d7b5 upstream.
The AK4396 DAC has a linear-scale attentuator, but
sound/pci/ice1712/prodigy_hifi.c used a log scale instead, which is
not
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Pavankumar Kondeti
commit 3d037774b42ed677f699b1dce7d548d55f4e4c2b upstream.
There is a possibility of QH overlay region having reference to a stale
qTD pointer during unlink.
Consider an endp
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Cox
commit 17c60c6b763cb5b83b0185e7d38d01d18e55a05a upstream.
This can also appear as 0x9192. Reported in bugzilla and confirmed with the
board documentation for these boards.
Resolves-bu
>
> The PHY framework provides a set of API's for the PHY drivers to
> create/remove a PHY and the PHY users to obtain a reference to the PHY
> using or without using phandle. If the PHY users has to obtain a
> reference to
> the PHY without using phandle, the platform specfic intialization code
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Bjørn Mork
commit 60e233a56609fd963c59e99bd75c663d63fa91b6 upstream.
Fengguang Wu writes:
> After the __devinit* removal series, I can still get kernel panic in
> show_uevent(). So there are
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit abf02cfc179bb4bd30d05f582d61b3b8f429b813 upstream.
64bit arches have a buggy r8712u driver, let's fix it.
skb->tail must be set properly or network stack behavior is undefi
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Jon Hunter
commit 54f32a35f4d3a653a18a2c8c239f19ae060bd803 upstream.
Calling the dmtimer function omap_dm_timer_set_source() fails if following a
call to pm_runtime_put() to disable the timer.
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: James Bottomley
commit 14216561e164671ce147458653b1fea06a4ada1e upstream.
This is a particularly nasty SCSI ATA Translation Layer (SATL) problem.
SAT-2 says (section 8.12.2)
if the de
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Adam Jackson
commit 23c99e775d14f01ba45a5affd2fb51af4328359c upstream.
Signed-off-by: Adam Jackson
Signed-off-by: Daniel Vetter
Signed-off-by: Ben Hutchings
---
drivers/gpu/drm/i915/intel_d
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit f39c1bfb5a03e2d255451bff05be0d7255298fa4 upstream.
Commit 43cedbf0e8dfb9c5610eb7985d5f21263e313802 (SUNRPC: Ensure that
we grab the XPRT_LOCK before calling xprt_alloc_sl
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: "Arnaud Patard (Rtp)"
commit 58569aee5a1a5dcc25c34a0a2ed9a377874e6b05 upstream.
The mv643xx ethernet controller limits the packet size for the TX
checksum offloading. This patch sets this limit
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Dirk Behme
commit 7be0670f7b9198382938a03ff3db7f47ef6b4780 upstream.
Remove the clock configuration from imx_setup_ufcr(). This
isn't needed here and will cause garbage output if done.
To be b
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Ãric Piel
commit dafc4f7be1a556ca3868d343c00127728b397068 upstream.
Commit b69cc672052540 added support for the E-861. After acquiring a C-867, I
realised that every Physik Instrumente's devi
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: "Alexis R. Cortes"
commit 71c731a296f1b08a3724bd1b514b64f1bda87a23 upstream.
This patch is intended to work around a known issue on the
SN65LVPE502CP USB3.0 re-driver that can delay the negotia
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Matthew Garrett
commit e955a1cd086de4d165ae0f4c7be7289d84b63bdc upstream.
My test platform (Intel DX79SI) boots reliably under BIOS, but frequently
crashes when booting via UEFI. I finally trac
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Santiago Leon
commit d90c92fee89ccd75ef2646f3bde0b4c0450666c3 upstream.
This patch fixes a bug found by Nish Aravamudan
(https://lkml.org/lkml/2012/5/15/220) where the driver is not following
t
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Kashyap Desai
commit bd8d6dd43a77bfd2b8fef5b094b9d6095e169dee upstream.
The following patch moves the poll_aen_lock initializer from
megasas_probe_one() to megasas_init(). This prevents a cras
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Shawn Guo
commit c944b0b9354ea06ffb0c8a7178949f1185f9f499 upstream.
Though commit 602bf40 (ARM: imx6: exit coherency when shutting down
a cpu) improves the stability of imx6q cpu hotplug a lot,
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: "sreekanth.re...@lsi.com"
commit 338b131a3269881c7431234855c93c219b0979b6 upstream.
If the specified max_queue_depth setting is less than the
expected number of internal commands, then driver w
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: John Stultz
This is a -stable backport of 4e8b14526ca7fb046a81c94002c1c43b6fdf0e9b
Unexpected behavior could occur if the time is set to a value large
enough to overflow a 64bit ktime_t (which
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit bf8801145c01ab600f8df66e8c879ac642fa5846 upstream.
>From ARM debug architecture v7.1 onwards, a watchpoint exception causes
the DFAR to be updated with the faulting data addr
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Gertjan van Wingerde
commit 6ced58a5dbb94dbfbea1b33ca3c56d1e929cd548 upstream.
The register is 16 bits wide, not 32.
Signed-off-by: Gertjan van Wingerde
Acked-by: Ivo Van Doorn
Signed-off-by
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Sarah Sharp
commit e95829f474f0db3a4d940cae1423783edd966027 upstream.
The Intel desktop boards DH77EB and DH77DF have a hardware issue that
can be worked around by BIOS. If the USB ports are s
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Chris Wilson
During modeset we have to disable the pipe to reconfigure its timings
and maybe its size. Userspace may have queued up command buffers that
depend upon the pipe running in a certain
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Konrad Rzeszutek Wilk
commit c96aae1f7f393387d160211f60398d58463a7e65 upstream.
When we are finished with return PFNs to the hypervisor, then
populate it back, and also mark the E820 MMIO and E
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Grazvydas Ignotas
commit c1c52848cef52e157468b8879fc3cae23b6f3a99 upstream.
omapfb does not currently set pseudo palette correctly for color depths
above 16bpp, making red text invisible, comma
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Shawn Guo
commit a46d2619d7180bda12bad2bf15bbd0731dfc2dcf upstream.
The binding doc and dts use properties "fsl,{cd,wp}-internal" while
esdhc driver uses "fsl,{cd,wp}-controller". Fix binding
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Gertjan van Wingerde
commit a396e10019eaf3809b0219c966865aaafec12630 upstream.
We need to program the rfkill switch GPIO pin direction to input at
device initialization time, not only when the
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Gertjan van Wingerde
commit 177ef8360fabdc49ff08d2598c06e7f7a36b53e3 upstream.
This is an RT3572 based device.
Signed-off-by: Maximilian Engelhardt
Signed-off-by: Gertjan van Wingerde
Acked-
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: John Stultz
This is a -stable backport of cee58483cf56e0ba355fdd97ff5e8925329aa936
Andreas Bombe reported that the added ktime_t overflow checking added to
timespec_valid in commit 4e8b14526ca7
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Sergei Poselenov
commit efd5d6b03bd9c9e0df646c56fb5f4f3e25e5c1ac upstream.
On our system (ARM Cortex-M3 SOC running linux-2.6.33)
frequent crashes were observed in the rt2800usb module
because
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Seth Jennings
commit 6d7d9798ad5c97ee4e911dd070dc12dc5ae55bd0 upstream.
This patch fixes a race condition that results in memory
corruption when using cleancache.
The race exists between the z
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Gariepy
commit 62004978df3898649e152751eb6ac264a323ec36 upstream.
Match the correct information which is DMI_PRODUCT_NAME instead of
DMI_BOARD_NAME
See dmidecode information on launchpad
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Lai Jiangshan
commit 96e65306b81351b656835c15931d1d237b252f27 upstream.
The compiler may compile the following code into TWO write/modify
instructions.
worker->flags &= ~WORKER_UNBOUND
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Yuval Mintz
[ Upstream commit 5c879d2094946081af934739850c7260e8b25d3c ]
Commit c3def943c7117d42caaed3478731ea7c3c87190e have added support for
new pci ids of the 57840 board, while failing to
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 94543a8d4fb302817014981489f15cb3b92ec3c2 upstream.
iwl_dbgfs_fh_reg_read() can cause crashes and/or
BUG_ON in slub because the ifdefs are wrong, the
code in iwl_dump_fh() s
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit f637c4c9405e21f44cf0045eaf77eddd3a79ca5a upstream.
The i.MX cpufreq implementation uses the CPU_FREQ_TABLE helpers,
so it needs to select that code to be built. This proble
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Luca Tettamanti
commit 43ca6cb28c871f2fbad10117b0648e5ae3b0f638 upstream.
The old interface is bugged and reads the wrong sensor when retrieving
the reading for the chassis fan (it reads the CP
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Jesse Barnes
commit acb4b992d8a13728044f430b47b9199aa45993e9 upstream.
Each of these error messages can be caused by a broken or malicious
userspace wanting to spam the dmesg with useless info.
1 - 100 of 297 matches
Mail list logo
