Just to sumarize the bug after poking before the patch:
systemd calls open/close on /dev/ttyS0 per line
atmel_shutdown executes on close
uart_timer_callback may fire during shutdown before timer is killed
tasklet gets scheduled after tasklet_kill
atmel_shutdown returns back to uart_c
swapoff clear swap_info's SWP_USED flag prematurely and free its resources
after that. A concurrent swapon will reuse this swap_info while its previous
resources are not cleared completely.
These late freed resources are:
- p->percpu_cluster
- swap_cgroup_ctrl[type]
- block_device setting
- inode-
On Wed, Jan 08, 2014 at 01:48:58PM +, Mel Gorman wrote:
> Adding LKML to the list as this -stable snifftest has identified an
> upstream regression.
>
> On Wed, Jan 08, 2014 at 10:43:40AM +, Mel Gorman wrote:
> > On Tue, Jan 07, 2014 at 08:30:12PM +, Mel Gorman wrote:
> > > On Tue, Jan
From: Sujith Manoharan
Fast Channel Change across bands was enabled for
AR9462 recently, but this is causing baseband issues.
Disable it until this feature is tested well. Also,
remove the feature bit for AR9565 since it is
a single-band card and doesn't support this feature.
Cc: stable@vger.ker
From: Sujith Manoharan
Accessing the current channel definition in mac80211
when processing RX packets is problematic because it
could have been updated when a scan is issued. Since a
channel change involves flushing the existing packets
in the RX queue before a chip-reset is done, they would
be
On 01/03/2014 03:29 PM, Sarah Sharp wrote:
> I'll let you know when I have some diagnostic patches ready.
Hi Sarah. I see today gregkh committed the patches you've already sent
me, so I assume someone (other than me) has tested those patches and
discovered some benefit from them?
I'm still wond
On Wed, Jan 08, 2014 at 08:19:24PM +0200, Tomas Winkler wrote:
> give up reseting after 3 unsuccessful tries
>
> Cc:
> Signed-off-by: Tomas Winkler
> Signed-off-by: Alexander Usyskin
> ---
> drivers/misc/mei/client.c | 1 +
> drivers/misc/mei/init.c| 10 ++
> drivers/misc/mei/me
On Wed, Jan 08, 2014 at 08:19:23PM +0200, Tomas Winkler wrote:
> 1. MEI_DEV_RESETTING device state spans only hardware reset flow
> while starting dev state is saved into a local variable for further
> reference, this let us to reduce big if statements in case we
> are trying to avoid nested resets
This is a note to let you know that I've just added the patch titled
mei: use hbm idle state to prevent spurious resets
to my char-misc git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
in the char-misc-next branch.
The patch will show up
On Wed, Jan 08, 2014 at 08:19:21PM +0200, Tomas Winkler wrote:
> This fixes a potential deadlock in case of a firmware
> initiated reset
>
> mei_reset has a dialog with the interrupt thread hence
> it has to be run from an another work item
>
> Most of the mei_resets were called from mei_hbm_disp
On Wed, Jan 08, 2014 at 08:19:23PM +0200, Tomas Winkler wrote:
> 1. MEI_DEV_RESETTING device state spans only hardware reset flow
> while starting dev state is saved into a local variable for further
> reference, this let us to reduce big if statements in case we
> are trying to avoid nested resets
Subject: + mm-fix-crash-when-using-xfs-on-loopback.patch added to -mm tree
To:
mpato...@redhat.com,a...@linux.intel.com,c...@linux.com,dave.ang...@bell.net,del...@gmx.de,iamjoonsoo@lge.com,penb...@kernel.org,stable@vger.kernel.org
From: a...@linux-foundation.org
Date: Wed, 08 Jan 2014 14:01:58
On Tue 07-01-14 12:57:17, Ted Tso wrote:
> A missing cast means that when we are truncating a file which is less
> than 60 bytes, we don't trunate the wrong area of memory, and in fact
> we can end up truncating the next inode in the inode table, or worse
> yet, some other kernel data structure.
Subject: + nilfs2-fix-segctor-bug-that-causes-file-system-corruption.patch
added to -mm tree
To: andreas.roh...@gmx.net,konishi.ryus...@lab.ntt.co.jp,stable@vger.kernel.org
From: a...@linux-foundation.org
Date: Wed, 08 Jan 2014 12:47:17 -0800
The patch titled
Subject: nilfs2: fix segctor bu
This is a note to let you know that I've just added the patch titled
xhci: Set scatter-gather limit to avoid failed block writes.
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-next branch.
The patch will show up in the n
This is a note to let you know that I've just added the patch titled
xhci: Avoid infinite loop when sg urb requires too many trbs
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-next branch.
The patch will show up in the n
nfc_nfc_free unlink clients from the device list
and has to be called under mei mutex
Signed-off-by: Tomas Winkler
Reviewed-by: Alexander Usyskin
---
drivers/misc/mei/nfc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/misc/mei/nfc.c b/drivers/misc/mei/nfc.c
index 0a89220..54961
diff --git a/Makefile b/Makefile
index 2d084a418789..8045c75414ae 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 4
-SUBLEVEL = 75
+SUBLEVEL = 76
EXTRAVERSION =
NAME = Saber-toothed Squirrel
diff --git a/arch/powerpc/include/asm/exception-64s.h
b/arch/powerpc/i
I'm announcing the release of the 3.4.76 kernel.
All users of the 3.4 kernel series must upgrade.
The updated 3.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.4.y
and can be browsed at the normal kernel.org git web browser:
This fixes a potential deadlock in case of a firmware
initiated reset
mei_reset has a dialog with the interrupt thread hence
it has to be run from an another work item
Most of the mei_resets were called from mei_hbm_dispatch
which is called in interrupt thread context so this
function underwent m
This series should address possible hiccup in
mei reset flow presenting itself as never ending
repetition of error line.
unexpected reset: dev_state = RESETTING
The patches make sure that stall watchdog doesn't jump in
prior to its time; second the reset flow won't recuse,
and at last it w
give up reseting after 3 unsuccessful tries
Cc:
Signed-off-by: Tomas Winkler
Signed-off-by: Alexander Usyskin
---
drivers/misc/mei/client.c | 1 +
drivers/misc/mei/init.c| 10 ++
drivers/misc/mei/mei_dev.h | 7 +++
3 files changed, 18 insertions(+)
diff --git a/drivers/mis
When reset is caused by hbm protocol mismatch or timeout
we might end up in an endless reset loop and hbm protocol
will never sync
Cc:
Signed-off-by: Tomas Winkler
Signed-off-by: Alexander Usyskin
---
drivers/misc/mei/hbm.c | 19 +++
drivers/misc/mei/hbm.h | 1 +
1. MEI_DEV_RESETTING device state spans only hardware reset flow
while starting dev state is saved into a local variable for further
reference, this let us to reduce big if statements in case we
are trying to avoid nested resets
2. During initializations if the reset ended in MEI_DEV_DISABLED devi
Hi Mel,
On Tue, Jan 07, 2014 at 02:00:35PM +, Mel Gorman wrote:
> A number of NUMA balancing patches were tagged for -stable but I got a
> number of rejected mails from either Greg or his robot minion. The list
> of relevant patches is
>
> FAILED: patch "[PATCH] mm: numa: serialise parallel
> From: Alan Stern
> On Wed, 8 Jan 2014, David Laight wrote:
>
> > > From: Alan Stern
> > >
> > > This may be a foolish question, but why is xhci-hcd using no-op TRBs in
> > > the first place?
> >
> > Because it can't write in a link TRB because other parts of the
> > code use link TRBs to detect
On Wed, 8 Jan 2014, David Laight wrote:
> > From: Alan Stern
> >
> > This may be a foolish question, but why is xhci-hcd using no-op TRBs in
> > the first place?
>
> Because it can't write in a link TRB because other parts of the
> code use link TRBs to detect the end of the ring.
>
> The probl
> From: Alan Stern
>
> This may be a foolish question, but why is xhci-hcd using no-op TRBs in
> the first place?
Because it can't write in a link TRB because other parts of the
code use link TRBs to detect the end of the ring.
The problem is that it can't put a link TRB in the middle of
a chain
On 08/01/2014 16:06, Gregory CLEMENT wrote:
> Hi,
>
> Here come the 5th version of the series fixing the i2c bus hang on A0
> version of the Armada XP SoCs. It occurred on the early release of the
> OpenBlocks AX3-4 boards. Indeed the first variants of Armada XP SoCs
> (A0 stepping) have issues re
On 12/11/2013 02:55 PM, Yinghai Lu wrote:
> On Wed, Dec 11, 2013 at 11:19 AM, Joseph Salisbury
> wrote:
>> On 12/09/2013 03:10 PM, Yinghai Lu wrote:
>>> On Mon, Dec 9, 2013 at 11:42 AM, Bjorn Helgaas wrote:
That doesn't answer my question at all.
I understand that this change makes
On Tue, 7 Jan 2014, Sarah Sharp wrote:
> On Tue, Jan 07, 2014 at 03:57:00PM -0800, walt wrote:
> > On 01/07/2014 01:21 PM, Sarah Sharp wrote:
> >
> > > Can you please try the attached patch, on top of the previous three
> > > patches, and send me dmesg?
> >
> > Hi Sarah, I just now finished runn
Ping.
> -Original Message-
> From: Vivek Goyal [mailto:vgo...@redhat.com]
> Sent: 12 December 2013 14:42
> To: Qais Yousef; Andrew Morton
> Cc: linux-ker...@vger.kernel.org; Michael Holzheu; linux-m...@linux-mips.org;
> stable@vger.kernel.org
> Subject: Re: [PATCH] crash_dump: fix compilat
From: Sujith Manoharan
Fast Channel Change across bands was enabled for
AR9462 recently, but this is causing baseband issues.
Disable it until this feature is tested well. Also,
remove the feature bit for AR9565 since it is
a single-band card and doesn't support this feature.
Cc: stable@vger.ker
From: Sujith Manoharan
Accessing the current channel definition in mac80211
when processing RX packets is problematic because it
could have been updated when a scan is issued. Since a
channel change involves flushing the existing packets
in the RX queue before a chip-reset is done, they would
be
> From: Sarah Sharp
> On Tue, Jan 07, 2014 at 03:57:00PM -0800, walt wrote:
> > On 01/07/2014 01:21 PM, Sarah Sharp wrote:
> >
> > > Can you please try the attached patch, on top of the previous three
> > > patches, and send me dmesg?
> >
> > Hi Sarah, I just now finished running 0001-More-debuggin
On Wed, Jan 08, 2014 at 03:53:28PM +0100, Daniel Vetter wrote:
> On Wed, Jan 08, 2014 at 11:12:27AM -0200, Paulo Zanoni wrote:
> > From: Paulo Zanoni
> >
> > Properly zero the refcounts and crtc->ddi_pll_set so the previous HW
> > state doesn't affect the result of reading the current HW state.
>
On Wednesday 08 January 2014, Gregory CLEMENT wrote:
> On 08/01/2014 16:21, Wolfram Sang wrote:
> >> diff --git a/drivers/i2c/busses/i2c-mv64xxx.c
> >> b/drivers/i2c/busses/i2c-mv64xxx.c
> >> index 8be7e42aa4de..f424c0f89946 100644
> >> --- a/drivers/i2c/busses/i2c-mv64xxx.c
> >> +++ b/drivers/i2
On 08/01/2014 16:22, Wolfram Sang wrote:
>> +new_compat->name = kstrdup("compatible", GFP_KERNEL);
>> +new_compat->length = sizeof("marvell,mv78230-a0-i2c");
>> +new_compat->value = kstrdup("marvell,mv78230-a0-i2c",
>> +
> >> + {
> >> + .compatible = "marvell,mv78230-a0-i2c",
> >> + .data = &mv64xxx_i2c_regs_mv64xxx
> >> + },
> >
> > I think a oneliner entry like the entries above is easier to read, but
> > that is very minor...
>
> By using one line we would break the 80 character rule,
> hat
On 08/01/2014 16:21, Wolfram Sang wrote:
> On Wed, Jan 08, 2014 at 04:06:28PM +0100, Gregory CLEMENT wrote:
>> The first variants of Armada XP SoCs (A0 stepping) have issues related
>> to the i2c controller which prevent to use the offload mechanism and
>> lead to a kernel hang during boot.
>>
>> T
> + new_compat->name = kstrdup("compatible", GFP_KERNEL);
> + new_compat->length = sizeof("marvell,mv78230-a0-i2c");
> + new_compat->value = kstrdup("marvell,mv78230-a0-i2c",
> + GFP_KERNEL);
> +
Very minor again: S
On Wed, Jan 08, 2014 at 04:06:28PM +0100, Gregory CLEMENT wrote:
> The first variants of Armada XP SoCs (A0 stepping) have issues related
> to the i2c controller which prevent to use the offload mechanism and
> lead to a kernel hang during boot.
>
> The commit introduces a new the compatible strin
On Wednesday 08 January 2014 16:06:25 Gregory CLEMENT wrote:
> Hi,
>
> Here come the 5th version of the series fixing the i2c bus hang on A0
> version of the Armada XP SoCs. It occurred on the early release of the
> OpenBlocks AX3-4 boards. Indeed the first variants of Armada XP SoCs
> (A0 steppin
The first variants of Armada XP SoCs (A0 stepping) have issues related
to the i2c controller which prevent to use the offload mechanism and
lead to a kernel hang during boot.
The commit introduces a new the compatible string
marvell,mv78230-a0-i2c for the i2c controller. When this compatible
strin
The first variants of Armada XP SoCs (A0 stepping) have issues related
to the i2c controller which prevent to use the offload mechanism and
lead to a kernel hang during boot.
This commit add quirk in the mvebu platform code to check the SoC
version and then update the compatible string for the i2c
The first variants of Armada XP SoCs (A0 stepping) have issues related
to the i2c controller which prevent to use the offload mechanism and
ead to a kernel hang during boot.
The commit introduces a new the compatible string
marvell,mv78230-a0-i2c for the i2c controller.
Signed-off-by: Gregory CLE
Hi,
Here come the 5th version of the series fixing the i2c bus hang on A0
version of the Armada XP SoCs. It occurred on the early release of the
OpenBlocks AX3-4 boards. Indeed the first variants of Armada XP SoCs
(A0 stepping) have issues related to the i2c controller which prevent
to use the off
All the mvebu SoCs have information related to their variant and
revision that can be read from the PCI control register.
This patch adds support for Armada XP and Armada 370. This reading of
the revision and the ID are done before the PCI initialization to
avoid any conflicts. Once these data are
On Wed, Jan 08, 2014 at 11:12:27AM -0200, Paulo Zanoni wrote:
> From: Paulo Zanoni
>
> Properly zero the refcounts and crtc->ddi_pll_set so the previous HW
> state doesn't affect the result of reading the current HW state.
>
> This fixes WARNs about WRPLL refcount if we have an HDMI monitor on
>
**Sorry for the duplicate mail, I forgot to force plain-text mode in
gmail or the mailing list rejects the mails. Sigh, I need to buy my
own email server at this rate to even deal with the mailing lists and
proper etiquette (no quoteS) :(
Ah, I forgot there was that third mode(no dma and no pdc).
On Wed, Jan 08, 2014 at 11:12:27AM -0200, Paulo Zanoni wrote:
> From: Paulo Zanoni
>
> Properly zero the refcounts and crtc->ddi_pll_set so the previous HW
> state doesn't affect the result of reading the current HW state.
>
> This fixes WARNs about WRPLL refcount if we have an HDMI monitor on
>
On Wed, Jan 08, 2014 at 05:56:21AM -0800, Guenter Roeck wrote:
> On 01/07/2014 02:00 PM, Shuah Khan wrote:
> > On 01/07/2014 12:16 PM, Greg Kroah-Hartman wrote:
> >> On Tue, Jan 07, 2014 at 12:07:14PM -0700, Shuah Khan wrote:
> >>> On 01/06/2014 03:36 PM, Greg Kroah-Hartman wrote:
> This is th
On 08/01/2014 13:55, Arnd Bergmann wrote:
> On Tuesday 07 January 2014, Gregory CLEMENT wrote:
>> diff --git a/include/linux/mvebu-soc-id.h b/include/linux/mvebu-soc-id.h
>> new file mode 100644
>> index ..31654252fe35
>> --- /dev/null
>> +++ b/include/linux/mvebu-soc-id.h
>> +#ifdef CO
On 08/01/2014 14:45, Arnd Bergmann wrote:
> On Wednesday 08 January 2014 14:39:59 Wolfram Sang wrote:
>>> However, when I first read this I thought it should be a -a0 specific
>>> compatible string, not a 'offload-broken' property - any idea what the
>>> DT consensus is here? I've seen
Hi Wolfram,
On 08/01/2014 14:39, Wolfram Sang wrote:
>
>> However, when I first read this I thought it should be a -a0 specific
>> compatible string, not a 'offload-broken' property - any idea what the
>> DT consensus is here? I've seen both approach in use ..
>
> I prefer the
On 01/07/2014 02:00 PM, Shuah Khan wrote:
On 01/07/2014 12:16 PM, Greg Kroah-Hartman wrote:
On Tue, Jan 07, 2014 at 12:07:14PM -0700, Shuah Khan wrote:
On 01/06/2014 03:36 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.12.7 release.
There are 144 patches i
Adding LKML to the list as this -stable snifftest has identified an
upstream regression.
On Wed, Jan 08, 2014 at 10:43:40AM +, Mel Gorman wrote:
> On Tue, Jan 07, 2014 at 08:30:12PM +, Mel Gorman wrote:
> > On Tue, Jan 07, 2014 at 10:54:40AM -0800, Greg KH wrote:
> > > On Tue, Jan 07, 2014
On Wednesday 08 January 2014 14:39:59 Wolfram Sang wrote:
> > However, when I first read this I thought it should be a -a0 specific
> > compatible string, not a 'offload-broken' property - any idea what the
> > DT consensus is here? I've seen both approach in use ..
> > >>>
> > >>> I
Hi Andrew,
> From: Andrew Lunn [mailto:and...@lunn.ch]
> Sent: Tuesday, December 31, 2013 7:05 PM
>
> On Tue, Dec 31, 2013 at 07:12:14AM -0500, Tejun Heo wrote:
> > On Mon, Dec 23, 2013 at 01:07:35PM +0100, Simon Guinot wrote:
> > > @@ -1358,6 +1359,7 @@ static int mv_scr_write(struct ata_link *l
On Wednesday 08 January 2014 14:42:45 Gregory CLEMENT wrote:
> You means something like the following code ?
>
> static void __init armada_370_xp_dt_init(void)
> {
> + if (of_machine_is_compatible("plathome,openblocks-ax3-4"))
> + i2c_quirk();
> of_platform_populate(NU
On 08/01/2014 13:52, Arnd Bergmann wrote:
> On Tuesday 07 January 2014, Gregory CLEMENT wrote:
>
>> static void __init armada_370_xp_dt_init(void)
>> {
>> + i2c_quirk();
>> of_platform_populate(NULL, of_default_bus_match_table, NULL, NULL);
>> }
>
> I'd prefer to enable the quirk
> However, when I first read this I thought it should be a -a0 specific
> compatible string, not a 'offload-broken' property - any idea what the
> DT consensus is here? I've seen both approach in use ..
> >>>
> >>> I prefer the replacement of the compatible string. If it should real
From: Paulo Zanoni
Properly zero the refcounts and crtc->ddi_pll_set so the previous HW
state doesn't affect the result of reading the current HW state.
This fixes WARNs about WRPLL refcount if we have an HDMI monitor on
HSW and then suspend/resume.
Cc: stable@vger.kernel.org
Bugzilla: https://
On 08/01/2014 12:29, Wolfram Sang wrote:
> On Wed, Jan 08, 2014 at 11:15:05AM +0100, Gregory CLEMENT wrote:
>> Hi Wolfram,
>>
>> On 08/01/2014 00:06, Wolfram Sang wrote:
>>> On Tue, Jan 07, 2014 at 11:38:53AM -0700, Jason Gunthorpe wrote:
On Tue, Jan 07, 2014 at 05:35:03PM +0100, Gregory CLEME
On Tuesday 07 January 2014, Gregory CLEMENT wrote:
> diff --git a/include/linux/mvebu-soc-id.h b/include/linux/mvebu-soc-id.h
> new file mode 100644
> index ..31654252fe35
> --- /dev/null
> +++ b/include/linux/mvebu-soc-id.h
> +#ifdef CONFIG_ARCH_MVEBU
> +int mvebu_get_soc_id(u32 *dev,
On Tuesday 07 January 2014, Gregory CLEMENT wrote:
> static void __init armada_370_xp_dt_init(void)
> {
> + i2c_quirk();
> of_platform_populate(NULL, of_default_bus_match_table, NULL, NULL);
> }
I'd prefer to enable the quirk only on machines that we know may be affected,
i.e.
O
On Tue, Jan 07, 2014 at 09:40:20AM +0900, Nobuhiro Iwamatsu wrote:
> Hi,
>
> This patch was committed to linus tree by
> ad70b029d2c678386384bd72c7fa2705c449b518.
> Could you review and apply this patch to stable tree?
>
> Best regards,
> Nobuhiro
I will queue this for the 3.11 kernel as well
On Wed, Jan 08, 2014 at 11:15:05AM +0100, Gregory CLEMENT wrote:
> Hi Wolfram,
>
> On 08/01/2014 00:06, Wolfram Sang wrote:
> > On Tue, Jan 07, 2014 at 11:38:53AM -0700, Jason Gunthorpe wrote:
> >> On Tue, Jan 07, 2014 at 05:35:03PM +0100, Gregory CLEMENT wrote:
> >>> +static struct property i2c_o
Hi Sage,
On Tue, Dec 31, 2013 at 08:21:19AM -0800, Sage Weil wrote:
> Hi Greg,
>
> This is a somewhat long overdue set of fixes for 3.10.y. Since there
> are a lot of patches, they can be pulled from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git
> for-stable-3.10.24
On Tue, Jan 07, 2014 at 08:30:12PM +, Mel Gorman wrote:
> On Tue, Jan 07, 2014 at 10:54:40AM -0800, Greg KH wrote:
> > On Tue, Jan 07, 2014 at 06:17:15AM -0800, Greg KH wrote:
> > > On Tue, Jan 07, 2014 at 02:00:35PM +, Mel Gorman wrote:
> > > > A number of NUMA balancing patches were tagge
The driver defines ADAU1701_SEROCTL_WORD_LEN_16 as 0x10 while it should be b10,
so 0x2. This patch fixes it.
Reported-by: Magnus Reftel
Signed-off-by: Lars-Peter Clausen
Cc: stable@vger.kernel.org
---
sound/soc/codecs/adau1701.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Marek Roszko
The uart timer will schedule a tasklet when it fires. It is possible that it
can fire inside _shutdown before it is killed in the dma and pdc cleanup
routines. This causes a tasklet that exists after the port is shutdown, so when
the kernel finally executes it, it panics as the
Hi Wolfram,
On 08/01/2014 00:06, Wolfram Sang wrote:
> On Tue, Jan 07, 2014 at 11:38:53AM -0700, Jason Gunthorpe wrote:
>> On Tue, Jan 07, 2014 at 05:35:03PM +0100, Gregory CLEMENT wrote:
>>> +static struct property i2c_offload_broken = {
>>> + .name = "offload-broken",
>>> +};
>>> +
>>> +static
On Tue, Jan 07, 2014 at 06:50:40PM +, Greg Kroah-Hartman wrote:
> On Tue, Jan 07, 2014 at 10:09:50AM +, Mark Rutland wrote:
> > Hi Greg,
> >
> > On Mon, Jan 06, 2014 at 10:39:15PM +, Greg Kroah-Hartman wrote:
> > > 3.10-stable review patch. If anyone has any objections, please let me
> pm_runtime_get/put_sync() can sleep so don't hold spinlock while
> calling them.
>
> This patch prevents a BUG() during system suspend when
> CONFIG_DEBUG_ATOMIC_SLEEP is enabled.
>
> Bug is present in Kernel versions v3.9 onwards.
>
> Reported-by: Tomi Valkeinen
> Signed-off-by: Roger Quadro
75 matches
Mail list logo
