From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, stable@vger.kernel.org
Subject: Re: [ 00/11] 3.4.53-stable review
Date: Thu, 11 Jul 2013 17:33:46 -0700 [thread overview]
Message-ID: <20130712003346.GA10248@kroah.com> (raw)
In-Reply-To: <CAP=VYLqgAF=RL9BcemhQH_qN8c8n9vud2QfPkMskH-rBMd35UA@mail.gmail.com>
On Thu, Jul 11, 2013 at 08:24:33PM -0400, Paul Gortmaker wrote:
> On Thu, Jul 11, 2013 at 6:11 PM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > This is the start of the stable review cycle for the 3.4.53 release.
> > There are 11 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 me know.
> >
> > Responses should be made by Sat Jul 13 22:04:03 UTC 2013.
> > 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/v3.0/stable-review/patch-3.4.53-rc1.gz
>
> Just happened to notice the v3.0 in the path vs. the 3.4 version.
> Wasn't sure that was intentional or not, so figured I'd mention it.
It's intentional, it's always been there, but I guess I could use the
3.x link instead, they both point to the same place.
thanks,
greg k-h
next prev parent reply other threads:[~2013-07-12 0:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 22:11 [ 00/11] 3.4.53-stable review Greg Kroah-Hartman
2013-07-11 22:11 ` [ 01/11] libceph: Fix NULL pointer dereference in auth client code Greg Kroah-Hartman
2013-07-11 22:11 ` [ 02/11] drivers/cdrom/cdrom.c: use kzalloc() for failing hardware Greg Kroah-Hartman
2013-07-11 22:11 ` [ 03/11] charger-manager: Ensure event is not used as format string Greg Kroah-Hartman
2013-07-11 22:11 ` [ 04/11] hpfs: better test for errors Greg Kroah-Hartman
2013-07-11 22:11 ` [ 05/11] block: do not pass disk names as format strings Greg Kroah-Hartman
2013-07-11 22:11 ` [ 06/11] crypto: sanitize argument for format string Greg Kroah-Hartman
2013-07-11 22:11 ` [ 07/11] MAINTAINERS: add stable_kernel_rules.txt to stable maintainer information Greg Kroah-Hartman
2013-07-24 5:09 ` Ben Hutchings
2013-07-24 5:30 ` Greg Kroah-Hartman
2013-07-11 22:11 ` [ 08/11] Revert "serial: 8250_pci: add support for another kind of NetMos Technology PCI 9835 Multi-I/O Controller" Greg Kroah-Hartman
2013-07-11 22:11 ` [ 09/11] nfsd4: fix decoding of compounds across page boundaries Greg Kroah-Hartman
2013-07-11 22:11 ` [ 10/11] SCSI: sd: Fix parsing of temporary cache mode prefix Greg Kroah-Hartman
2013-07-11 22:11 ` [ 11/11] Revert "sched: Add missing call to calc_load_exit_idle()" Greg Kroah-Hartman
2013-07-12 0:24 ` [ 00/11] 3.4.53-stable review Paul Gortmaker
2013-07-12 0:33 ` Greg Kroah-Hartman [this message]
2013-07-12 2:17 ` Steven Rostedt
2013-07-12 14:58 ` Benjamin LaHaise
2013-07-12 15:08 ` Greg Kroah-Hartman
2013-07-12 17:21 ` Shuah Khan
2013-07-12 17:34 ` Guenter Roeck
2013-07-12 18:38 ` Greg Kroah-Hartman
2013-07-13 4:16 ` Satoru Takeuchi
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=20130712003346.GA10248@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).