From: NeilBrown <neilb@suse.de>
To: Igor M Podlesny <for.poige+lsr@gmail.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
stable@vger.kernel.org,
Jose Manuel dos Santos Calhariz <jose.calhariz@netvisao.pt>,
linux-raid@vger.kernel.org
Subject: Re: commit backport request
Date: Tue, 17 Jul 2012 13:43:37 +1000 [thread overview]
Message-ID: <20120717134337.751cd3e4@notabene.brown> (raw)
In-Reply-To: <CA+sTkh6Nnfx3OAF0CN0CfRCUHUg2XEtivY-DmTXrRGwnPLgY2Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 694 bytes --]
On Tue, 17 Jul 2012 11:26:41 +0800 Igor M Podlesny <for.poige+lsr@gmail.com>
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.
>
> --
Given that the date on:
commit 8432d2280bd7558fde3a0385d1b35c947197d754
Author: Ben Hutchings <ben@decadent.org.uk>
Date: Thu Jul 12 04:32:21 2012 +0100
Linux 3.2.23
is before the date on Ben's email (by a few hours), I suspect it is queued for
3.2.24.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-07-17 3:43 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 [this message]
2012-07-17 3:48 ` Ben Hutchings
2012-07-20 2:38 ` Igor M Podlesny
2012-07-20 2:58 ` NeilBrown
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=20120717134337.751cd3e4@notabene.brown \
--to=neilb@suse.de \
--cc=ben@decadent.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).