public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jon Mason <jon.mason@intel.com>
Cc: Jonghwan Choi <jhbird.choi@gmail.com>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	stable@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jonghwan Choi <jhbird.choi@samsung.com>
Subject: Re: [PATCH 3.9-stable] ntb: off by one sanity checks
Date: Wed, 22 May 2013 10:13:35 -0700	[thread overview]
Message-ID: <20130522171335.GA20889@kroah.com> (raw)
In-Reply-To: <20130520165129.GD31363@jonmason-lab>

On Mon, May 20, 2013 at 09:51:29AM -0700, Jon Mason wrote:
> On Mon, May 20, 2013 at 09:38:50AM -0700, Greg KH wrote:
> > On Sat, May 18, 2013 at 07:47:09AM -0700, Jon Mason wrote:
> > > On Sat, May 18, 2013 at 11:35:38AM +0900, Jonghwan Choi wrote:
> > > > From: Dan Carpenter <dan.carpenter@oracle.com>
> > > > 
> > > > This patch looks like it should be in the 3.9-stable tree, should we apply
> > > > it?
> > > 
> > > Yes, please do.  I'll respond to each of the patch series, but please
> > > apply them all.  Also, one patch was omitted from these, titled 
> > > NTB: variable dereferenced before check
> > > 
> > > Please include that patch in 3.9 stable as well.
> > 
> > Can you just send me the git commit ids of the patches you wish to see
> > applied to the stable tree, and the order in which they need to go in?
> 
> My apologies.  All the commits to Linus' tree were bug fixes, so all
> of them should be pulled.  You can get them at:
> 
> git://github.com/jonmason/ntb.git tags/ntb-bugfixes-3.10
> 
> or, if you just want the commit ids (in order of oldest to newest)
> 
> 186f27ff9f9ec5c110739ced88ce9f8fca053882
> ad3e2751e7c546ae678be1f8d86e898506b42cef
> cc0f868d8adef7bdc12cda132654870086d766bc

These are bugfixes.

> 113fc505b83b2d16e820ca74fa07f99a34877b1d

This is a new feature, not a -stable candidate.


> b77b2637b39ecc380bb08992380d7d48452b0872

Ugh, but this one, needs the previous one :(

> 90f9e934647e652a69396e18c779215a493271cf
> c9d534c8cbaedbb522a1d2cb037c6c394f610317
> c336acd3331dcc191a97dbc66a557d47741657c7
> 904435cf76a9bdd5eb41b1c4e049d5a64f3a8400
> 8b19d450ad188d402a183ff4a4d40f31c3916fbf

All bugfixes.  Ok, I've now applied them all, thanks.

greg k-h

      reply	other threads:[~2013-05-22 17:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-18  2:35 [PATCH 3.9-stable] ntb: off by one sanity checks Jonghwan Choi
2013-05-18 14:47 ` Jon Mason
2013-05-20 16:38   ` Greg KH
2013-05-20 16:51     ` Jon Mason
2013-05-22 17:13       ` Greg KH [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=20130522171335.GA20889@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dan.carpenter@oracle.com \
    --cc=jhbird.choi@gmail.com \
    --cc=jhbird.choi@samsung.com \
    --cc=jon.mason@intel.com \
    --cc=linux-kernel@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