public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Jens Axboe <jaxboe@fusionio.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	torsten.hilbrich@secunet.com, Nick Piggin <npiggin@kernel.dk>
Subject: Re: [patch] block: fix off-by-one in init_page_buffers
Date: Thu, 21 Jun 2012 16:45:18 +0100	[thread overview]
Message-ID: <20120621154518.GR2753@decadent.org.uk> (raw)
In-Reply-To: <x49txy5yi9z.fsf@segfault.boston.devel.redhat.com>

On Wed, Jun 20, 2012 at 02:01:28PM -0400, Jeff Moyer wrote:
[...]
> This needs backporting to the stable trees where the offending commit
> was backported.  I'm sure that includes 3.0 and 3.3, but not sure where
> else it was committed.

3.2 as well.

> Is there an easy way to tell what trees got the commit?
[...]

I don't know about easy, but if you have 'stable' as a remote then
this works:

$ git branch -r | sed 's/^ *stable\/linux-\([0-9.]*\)\.y/\1/; t; d' | while read version; do git rev-list --grep=080399aaaf3531f5b8761ec0ac30ff98891e8686 v$version..stable/linux-$version.y | grep -q . && echo $version; done
3.0
3.2
3.3

(Maybe I'll wrap that up in a script.)
 
Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
                                                              - Albert Camus

      reply	other threads:[~2012-06-21 15:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 18:01 [patch] block: fix off-by-one in init_page_buffers Jeff Moyer
2012-06-21 15:45 ` Ben Hutchings [this message]

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=20120621154518.GR2753@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=jaxboe@fusionio.com \
    --cc=jmoyer@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@kernel.dk \
    --cc=stable@vger.kernel.org \
    --cc=torsten.hilbrich@secunet.com \
    /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