public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sven-Haegar Koch <haegar@sdinet.de>
Cc: stable@vger.kernel.org,
	Linux-Kernel-Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.32.55+ printk_ratelimit()
Date: Mon, 13 Feb 2012 13:44:31 -0800	[thread overview]
Message-ID: <20120213214431.GA11443@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1202132148450.32459@aurora.sdinet.de>

On Mon, Feb 13, 2012 at 09:58:08PM +0100, Sven-Haegar Koch wrote:
> hello,
> 
> catching up with the stable kernel 2.6.32 I saw that 2.6.32.55 included 
> 8a64f33 "kernel.h: add printk_ratelimited and pr_<level>_rl"
> 
> Could it be that 2.6.32.x now also should get upstream 
> d8521fcc5e0ad3e79bbc4231bb20a6cdc2b50164 "printk_ratelimited(): fix 
> uninitialized spinlock" ?

Yes, I've now queued that one up, as well as another printk_ratelimit
fix that is needed.

thanks for letting me know.

greg k-h

      reply	other threads:[~2012-02-13 21:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13 20:58 2.6.32.55+ printk_ratelimit() Sven-Haegar Koch
2012-02-13 21:44 ` Greg KH [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=20120213214431.GA11443@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=haegar@sdinet.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.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