public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: Chris Wright <chrisw@sous-sol.org>,
	stable@kernel.org, torvalds@osdl.org,
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.17.1
Date: Tue, 20 Jun 2006 09:23:15 -0400	[thread overview]
Message-ID: <20060620132310.GA3114@tuxdriver.com> (raw)
In-Reply-To: <200606201256.27252.mb@bu3sch.de>

On Tue, Jun 20, 2006 at 12:56:26PM +0200, Michael Buesch wrote:
> On Tuesday 20 June 2006 12:44, Chris Wright wrote:
> > * Michael Buesch (mb@bu3sch.de) wrote:
> > > On Tuesday 20 June 2006 12:13, Chris Wright wrote:
> > > > We (the -stable team) are announcing the release of the 2.6.17.1 kernel.
> > > 
> > > Please consider inclusion of the following patch into 2.6.17.2:
> > > 
> > > It fixes a possible crash. Might be triggerable in networks with
> > > heavy traffic. I only saw it once so far, though.
> > 
> > I didn't notice that it made it to Linus' tree yet.  Can you make sure
> > to push it up, and I'll queue it for -stable.
> 
> It is in -mm and I think John Linville also queued it upstream
> through Jeff to Linus.
> >From my perspective, everything is done ;)

I haven't quite done my part yet, but I intend to do so.  I think
this is a fine candidate for -stable.

John
-- 
John W. Linville
linville@tuxdriver.com

      parent reply	other threads:[~2006-06-20 13:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20 10:13 Linux 2.6.17.1 Chris Wright
2006-06-20 10:14 ` Chris Wright
2006-06-20 10:35 ` Michael Buesch
2006-06-20 10:44   ` Chris Wright
2006-06-20 10:56     ` Michael Buesch
2006-06-20 10:57       ` Chris Wright
2006-06-20 13:23       ` John W. Linville [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=20060620132310.GA3114@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=chrisw@sous-sol.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=stable@kernel.org \
    --cc=torvalds@osdl.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