From: NeilBrown <neilb@suse.de>
To: Igor M Podlesny <for.poige+lsr@gmail.com>
Cc: linux-raid@vger.kernel.org, stable@vger.kernel.org,
Jose Manuel dos Santos Calhariz <jose.calhariz@netvisao.pt>
Subject: Re: commit backport request
Date: Fri, 20 Jul 2012 12:58:34 +1000 [thread overview]
Message-ID: <20120720125834.62c67b94@notabene.brown> (raw)
In-Reply-To: <CA+sTkh43mpEiL5bUhx=tak3gO+Mg1W3-3A3zbScR8op2iKKyXQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
On Fri, 20 Jul 2012 10:38:50 +0800 Igor M Podlesny <for.poige+lsr@gmail.com>
wrote:
> On 17 July 2012 11:48, Ben Hutchings <ben@decadent.org.uk> wrote:
> > On Tue, 2012-07-17 at 11:26 +0800, Igor M Podlesny wrote:
> >> On 12 July 2012 11:52, Ben Hutchings <ben@decadent.org.uk> wrote:
> >> > On Mon, 2012-07-09 at 14:02 +1000, NeilBrown wrote:
> >> [...]
> >> > Queued up for 3.2.y, thanks.
> >> >
> >> > Ben.
> >>
> >> Hm, it looks like 3.2.23 misses it — at least my during rebase the
> >> cherry-picked fix applied again cleanly.
> >
> > I queued it up some hours after tagging that release. I *announced* the
> > release later, but that's because uploading tarballs etc. involves a
> > round trip via Greg.
> >
> > Ben.
>
> JFYI, 3.4.6 doesn't have it either...
>
> commit 1c8f63c2758096c3b6425f4ecb274901151d6f17
> Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Date: Thu Jul 19 12:11:49 2012 -0700
>
> Linux 3.4.6
>
> --
Yes it does.
commit 5bbbd747918d241b41f3220ff26323d7ed943c52
Author: Shaohua Li <shli@kernel.org>
Date: Tue Jul 3 15:57:19 2012 +1000
raid5: delayed stripe fix
commit fab363b5ff502d1b39ddcfec04271f5858d9f26e upstream.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-07-20 2:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 4:02 commit backport request NeilBrown
2012-07-09 5:08 ` Igor M Podlesny
2012-07-09 5:19 ` NeilBrown
2012-07-11 22:07 ` Greg KH
2012-07-12 4:14 ` NeilBrown
2012-07-12 21:28 ` Alexander Lyakas
2012-07-16 3:23 ` NeilBrown
2012-07-16 8:59 ` Alexander Lyakas
2012-07-12 3:52 ` Ben Hutchings
2012-07-17 3:26 ` Igor M Podlesny
2012-07-17 3:43 ` NeilBrown
2012-07-17 3:48 ` Ben Hutchings
2012-07-20 2:38 ` Igor M Podlesny
2012-07-20 2:58 ` NeilBrown [this message]
2012-07-20 6:35 ` Igor M Podlesny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120720125834.62c67b94@notabene.brown \
--to=neilb@suse.de \
--cc=for.poige+lsr@gmail.com \
--cc=jose.calhariz@netvisao.pt \
--cc=linux-raid@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.