From: Thomas Backlund <tmb@mageia.org>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org,
stable-review@kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [0/6] 2.6.33.18-longterm review
Date: Sat, 13 Aug 2011 23:12:19 +0300 [thread overview]
Message-ID: <4E46DAA3.4050706@mageia.org> (raw)
In-Reply-To: <20110812211045.GA6497@kroah.com>
Greg KH skrev 13.8.2011 00:10:
> This is the start of the stable review cycle for the 2.6.33.18 release.
> There are 6 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let us know. If anyone is a maintainer of the proper subsystem, and
> wants to add a Signed-off-by: line to the patch, please respond with it.
>
> Responses should be made by Monday, August 15, 2011, 20:00:00 UTC.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> kernel.org/pub/linux/kernel/v2.6/stable-review/patch-2.6.33.19-rc1.gz
URL is wrong (and patch version above is wrong too)...
Correct one is:
kernel.org/pub/linux/kernel/v2.6/longterm-review/patch-2.6.33.18-rc1.gz
--
Thomas
prev parent reply other threads:[~2011-08-13 20:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 21:10 [0/6] 2.6.33.18-longterm review Greg KH
2011-08-12 21:09 ` [1/6] crypto: Move md5_transform to lib/md5.c Greg KH
2011-08-12 21:09 ` [2/6] net: Compute protocol sequence numbers and fragment IDs using MD5 Greg KH
2011-08-12 21:09 ` [3/6] ALSA: timer - Fix Oops at closing slave timer Greg KH
2011-08-12 21:09 ` [4/6] ALSA: snd-usb-caiaq: Fix keymap for RigKontrol3 Greg KH
2011-08-12 21:09 ` [5/6] powerpc: Fix device tree claim code Greg KH
2011-08-12 21:09 ` [6/6] powerpc: pseries: Fix kexec on machines with more than 4TB of RAM Greg KH
2011-08-13 20:12 ` Thomas Backlund [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=4E46DAA3.4050706@mageia.org \
--to=tmb@mageia.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable-review@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.