public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org, stable@kernel.org
Subject: Linux 2.6.20.6
Date: Fri, 6 Apr 2007 13:29:48 -0700	[thread overview]
Message-ID: <20070406202948.GU10574@sequoia.sous-sol.org> (raw)

We (the -stable team) are announcing the release of the 2.6.20.6 kernel.
This has 2 important fixes that should have been in 2.6.20.5.  They are
issues that were pointed with 2.6.20.5 patches during its review cycle,
but the patch updates were mistakenly dropped.  Please accept our
apologies for the mistake.

The diffstat and short summary of the fixes are below.

I'll also be replying to this message with a copy of the patch between
2.6.20.5 and 2.6.20.6.

The updated 2.6.20.y git tree can be found at:
        git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.20.y.git
and can be browsed at the normal kernel.org git web browser:
        www.kernel.org/git/

thanks,
-chris
--------

 Makefile                    |    2 +-
 crypto/scatterwalk.c        |    2 +-
 include/asm-um/common.lds.S |    2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

Summary of changes from v2.6.20.5 to v2.6.20.6
==============================================

Chris Wright (1):
      Linux 2.6.20.6

Herbert Xu (1):
      CRYPTO api: Use the right value when advancing scatterwalk_copychunks

Paolo 'Blaisorblade' Giarrusso (1):
      uml: fix static linking for real


             reply	other threads:[~2007-04-06 20:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-06 20:29 Chris Wright [this message]
2007-04-06 20:30 ` Linux 2.6.20.6 Chris Wright
2007-04-09 16:14 ` Chuck Ebbert
2007-04-09 16:42   ` Chuck Ebbert
2007-04-09 17:34     ` Chris Wright
2007-04-09 17:21   ` [stable] " Chris Wright

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=20070406202948.GU10574@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.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