3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mikulas Patocka
commit 694617474e33b8603fc76e090ed7d09376514b1a upstream.
The patch 3e374919b314f20e2a04f641ebc1093d758f66a4 is supposed to fix the
problem where kmem_cache_create inco
3.13.11.6 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mikulas Patocka
commit 694617474e33b8603fc76e090ed7d09376514b1a upstream.
The patch 3e374919b314f20e2a04f641ebc1093d758f66a4 is supposed to fix the
problem where kmem_cache_create incor
From: Mikulas Patocka
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 694617474e33b8603fc76e090ed7d09376514b1a upstream.
The patch 3e374919b314f20e2a04f641ebc1093d758f66a4 is supposed to fix the
problem where kmem_cache_create incorrectly rep
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit 694617474e33b8603fc76e090ed7d09376514b1a upstream.
The patch 3e374919b314f20e2a04f641ebc1093d758f66a4 is supposed to fix the
problem where kmem_cache_create incorrectly
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit 694617474e33b8603fc76e090ed7d09376514b1a upstream.
The patch 3e374919b314f20e2a04f641ebc1093d758f66a4 is supposed to fix the
problem where kmem_cache_create incorrectly
3.15-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit 694617474e33b8603fc76e090ed7d09376514b1a upstream.
The patch 3e374919b314f20e2a04f641ebc1093d758f66a4 is supposed to fix the
problem where kmem_cache_create incorrectly
From: Mikulas Patocka
The patch 3e374919b314f20e2a04f641ebc1093d758f66a4 is supposed to fix the
problem where kmem_cache_create incorrectly reports duplicate cache name
and fails. The problem is described in the header of that patch.
However, the patch doesn't really fix the problem because of t
On Fri, May 23 2014 at 5:28pm -0400,
Pekka Enberg wrote:
> On 05/23/2014 11:16 PM, Mike Snitzer wrote:
> >On Tue, Mar 25 2014 at 2:07pm -0400,
> >Christoph Lameter wrote:
> >
> >>On Tue, 25 Mar 2014, Mike Snitzer wrote:
> >>
> >>>This patch still isn't upstream. Who should be shepherding it t
On Fri, May 23 2014 at 5:28pm -0400,
Pekka Enberg wrote:
> On 05/23/2014 11:16 PM, Mike Snitzer wrote:
> >On Tue, Mar 25 2014 at 2:07pm -0400,
> >Christoph Lameter wrote:
> >
> >>On Tue, 25 Mar 2014, Mike Snitzer wrote:
> >>
> >>>This patch still isn't upstream. Who should be shepherding it t
On 05/23/2014 11:16 PM, Mike Snitzer wrote:
On Tue, Mar 25 2014 at 2:07pm -0400,
Christoph Lameter wrote:
On Tue, 25 Mar 2014, Mike Snitzer wrote:
This patch still isn't upstream. Who should be shepherding it to Linus?
Pekka usually does that.
Acked-by: Christoph Lameter
This still has
On Tue, Mar 25 2014 at 2:07pm -0400,
Christoph Lameter wrote:
> On Tue, 25 Mar 2014, Mike Snitzer wrote:
>
> > This patch still isn't upstream. Who should be shepherding it to Linus?
>
> Pekka usually does that.
>
> Acked-by: Christoph Lameter
This still hasn't gotten upstream.
Pekka, any
On Tue, 25 Mar 2014, Mike Snitzer wrote:
> This patch still isn't upstream. Who should be shepherding it to Linus?
Pekka usually does that.
Acked-by: Christoph Lameter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.o
[Sorry for top-post but...]
This patch still isn't upstream. Who should be shepherding it to Linus?
Without it we're seeing crashes on Fedora when running regression tests
that use dm-raid (dm target that wraps MD raid), e.g.:
6,484484,682379136295,-;md: mdX: recovery done.
6,484485,68237914530
13 matches
Mail list logo