If the glue layer is removed first (core layer later),
it deletes the phy device first, then the core device.
But at core's removal, it still uses PHY's resources, it may
cause kernel's oops. It is much like the problem
Paul Zimmerman reported at:
http://marc.info/?l=linux-usb&m=136547502011472&w=2
If the glue layer is removed first (core layer later),
it deletes the phy device first, then the core device.
But at core's removal, it still uses PHY's resources, it may
cause kernel's oops. It is much like the problem
Paul Zimmerman reported at:
http://marc.info/?l=linux-usb&m=136547502011472&w=2
OK, here is clearer stack output from the run.
CAI Qian
+ ./check
FSTYP -- xfs (non-debug)
PLATFORM -- Linux/s390x ibm-z10-23 3.9.3
001 29s
002 3s
003 2s
004 [not run] this test requires a valid $SCRATCH_DEV
005 2s
006 9s
007 10s
008 7s
009
This patch looks like it should be in the 3.9-stable tree, should we apply
it?
--
From: "Wei Yongjun "
commit 3b813798aa7030f1beef638c75f8b0008f737a82 upstream
Fix to return -EINVAL in the i2c device found error handling
case instead of 0, as done elsewhere in this function.
And
This patch looks like it should be in the 3.9-stable tree, should we apply
it?
--
From: "Michał Mirosław "
commit c80712c793febdf1b13ad0e1c71a051e071b3fd8 upstream
This fixes 'preenable failed: -EINVAL' error when using this driver.
Signed-off-by: Michał Mirosław "
Signed-off-b
On Tue, May 21, 2013 at 10:50:21AM +0900, Tejun Heo wrote:
> When cgroup_next_descendant_pre() initiates a walk, it checks whether
> the subtree root doesn't have any children and if not returns NULL.
> Later code assumes that the subtree isn't empty. This is broken
> because the subtree may becom
Subject: +
ocfs2-goto-out_unlock-if-ocfs2_get_clusters_nocache-failed-in-ocfs2_fiemap.patch
added to -mm tree
To:
joseph...@huawei.com,jeff@oracle.com,jl...@evilplan.org,mfas...@suse.com,stable@vger.kernel.org
From: a...@linux-foundation.org
Date: Thu, 23 May 2013 16:07:52 -0700
The patch
On 05/22/2013 02:43 AM, Matt Fleming wrote:
> From: Matt Fleming
>
> pcibios_add_device() assumes that the physical addresses stored in
> setup_data are accessible via the direct kernel mapping, and that
> calling phys_to_virt() is valid. This isn't guaranteed to be true on x86
> where the direct
From: Johannes Berg
Unfortunately, advertising P2P_DEVICE support was a little
premature, a number of issues came up in testing and have
been fixed for 3.10. Rather than try to backport all the
different fixes, disable P2P_DEVICE support in the drivers
using it. For iwlmvm that implies disabling
From: Johannes Berg
Unfortunately, advertising P2P_DEVICE support was a little
premature, a number of issues came up in testing and have
been fixed for 3.10. Rather than try to backport all the
different fixes, disable P2P_DEVICE support in the drivers
using it.
Signed-off-by: Johannes Berg
---
On Thu, May 23, 2013 at 04:52:48PM +, Shuah Khan wrote:
> On Wed, 2013-05-22 at 15:10 -0700, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.9.4 release.
> > There are 21 patches in this series, all will be posted as a response
> > to this one. If anyone ha
On Wed, 2013-05-22 at 15:19 -0700, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.0.80 release.
> There are 3 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.
>
> Re
On Wed, 2013-05-22 at 15:18 -0700, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.4.47 release.
> There are 5 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.
>
> Re
On Wed, 2013-05-22 at 15:10 -0700, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.9.4 release.
> There are 21 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.
>
> Re
Am 23.05.2013 14:35, schrieb Matthew O'Connor:
> On 05/23/2013 06:24 AM, Smart Weblications GmbH - Florian Wiessner wrote:
>> Hm, i tried to apply it to 3.4.46 but it does not work:
>>
>> node02:/ocfs2/usr/src/linux-3.4.46# patch -p1 <../bridge-patch-3.4.46
>> patching file drivers/net/bonding/bond
Hi!
(the 3.2 version is different,
and it's instaging. (at not used by distros anyway))
No: used
Linux Kernel v3.2 used in:
-- SlackWare 14.00
This is actual stable version SlackWare
Please, backport all(!) needed patches
I'm download https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.2.
On 05/23/2013 06:24 AM, Smart Weblications GmbH - Florian Wiessner wrote:
> node02:/ocfs2/usr/src/linux-3.4.46# cat drivers/net/bonding/bond_alb.c.rej
My most sincere apologies - one more time, from a different mail server
that hopefully won't go around changing my attachments. If this doesn't
wor
On 05/23/2013 06:24 AM, Smart Weblications GmbH - Florian Wiessner wrote:
> Hm, i tried to apply it to 3.4.46 but it does not work:
>
> node02:/ocfs2/usr/src/linux-3.4.46# patch -p1 <../bridge-patch-3.4.46
> patching file drivers/net/bonding/bond_alb.c
> Hunk #1 FAILED at 704.
> 1 out of 1 hunk FAI
Am 23.05.2013 01:17, schrieb Matthew O'Connor:
> This is the backported patch I submitted previously. Hopefully this
> time around it won't be too messed up, I'm using Thunderbird instead of
> the web interface. I have applied it successfully and without warnings
> against 3.4.46. It builds, but
I am announcing the release of the 3.5.7.13 tree of stable patches.
This tree picks up the latest 3.5 stable release upstream, and add patches
on top that were later marked for stable but can't be added to 3.5, as
it is not anymore an stable series maintained upstream.
The tree is maintained by t
20 matches
Mail list logo
