linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shuah Khan <shuahkhan@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, stable@vger.kernel.org
Subject: Re: [ 0/1] 3.4.33-stable review
Date: Mon, 18 Feb 2013 19:50:16 -0700	[thread overview]
Message-ID: <CAKocOOPShXASvWEJw7r_NxTAKYA34DH9BiaEKo0saWEobar9zQ@mail.gmail.com> (raw)
In-Reply-To: <20130218181454.615592566@linuxfoundation.org>

On Mon, Feb 18, 2013 at 11:24 AM, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
> This is the start of the stable review cycle for the 3.4.33 release.
> There is 1 patch in this series, which will be posted as a response to
> this one.  If anyone has any issues with it being applied, please let me
> know.
>
> Responses should be made by Wed Feb 20 18:13:44 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.33-rc1.gz
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
> -------------

Patches applied cleanly to 3.0.65, and 3.4.32
Compiled and booted on the following systems:
HP EliteBook 6930p Intel(R) Core(TM)2 Duo CPU T9400 @ 2.53GHz
HP ProBook 6475b AMD A10-4600M APU with Radeon(tm) HD Graphics

Reviewed patches

Skipped Cross-compile tests

-- Shuah

  parent reply	other threads:[~2013-02-19  2:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 18:24 [ 0/1] 3.4.33-stable review Greg Kroah-Hartman
2013-02-18 18:24 ` [ 1/1] printk: fix buffer overflow when calling log_prefix function from call_console_drivers Greg Kroah-Hartman
2013-02-20 13:02   ` Satoru Takeuchi
2013-02-20 13:43     ` Alexandre SIMON
2013-02-20 15:56       ` Satoru Takeuchi
2013-02-19  2:50 ` Shuah Khan [this message]
2013-02-20  2:51   ` [ 0/1] 3.4.33-stable review Greg Kroah-Hartman
2013-02-20  3:31     ` Shuah Khan
2013-02-20 13:09       ` 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=CAKocOOPShXASvWEJw7r_NxTAKYA34DH9BiaEKo0saWEobar9zQ@mail.gmail.com \
    --to=shuahkhan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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).