From: Joe Perches <joe@perches.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: richard -rw- weinberger <richard.weinberger@gmail.com>,
Christian Dietrich
<christian.dietrich@informatik.uni-erlangen.de>,
"Venkatesh Pallipadi (Venki)" <venki@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Kevin Tian <kevin.tian@intel.com>,
Fengzhe Zhang <fengzhe.zhang@intel.com>,
John Stultz <johnstul@us.ibm.com>,
Lucas De Marchi <lucas.demarchi@profusion.mobi>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
lguest@lists.ozlabs.org, trivial@kernel.org
Subject: Re: [PATCH 8/8] arch/x86: use printk_ratelimited instead of printk_ratelimit
Date: Mon, 06 Jun 2011 20:37:25 -0700 [thread overview]
Message-ID: <1307417845.4994.57.camel@Joe-Laptop> (raw)
In-Reply-To: <87mxhugwu1.fsf@rustcorp.com.au>
On Tue, 2011-06-07 at 12:41 +0930, Rusty Russell wrote:
> On Mon, 6 Jun 2011 10:11:53 +0200, richard -rw- weinberger <richard.weinberger@gmail.com> wrote:
> > printk_ratelimited() needs DEFINE_RATELIMIT_STATE() which is defined
> > in ratelimit.h.
> Yech. I'm assuming that making printk.h include ratelimit.h makes a
> nasty mess?
Yup.
I proposed moving the <foo>_ratelimited dclarations to
ratelimited.h without any comment.
http://lkml.org/lkml/2010/2/18/377
prev parent reply other threads:[~2011-06-07 3:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1307199715.git.christian.dietrich@informatik.uni-erlangen.de>
2011-06-04 15:37 ` [PATCH 8/8] arch/x86: use printk_ratelimited instead of printk_ratelimit Christian Dietrich
[not found] ` <fce87f1efab55e15e91b21f1b73f0e86016a27d9.1307199715.git.christian.dietrich@informatik.uni-erlangen.de>
2011-06-06 6:35 ` Rusty Russell
[not found] ` <874o43ii1m.fsf@rustcorp.com.au>
2011-06-06 8:11 ` richard -rw- weinberger
[not found] ` <BANLkTinS67qH-pm2=Z9G1UXk4OOuZNsN9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-07 3:11 ` Rusty Russell
2011-06-07 3:37 ` Joe Perches [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=1307417845.4994.57.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=avi@redhat.com \
--cc=christian.dietrich@informatik.uni-erlangen.de \
--cc=fengzhe.zhang@intel.com \
--cc=hpa@zytor.com \
--cc=johnstul@us.ibm.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=lguest@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=richard.weinberger@gmail.com \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=trivial@kernel.org \
--cc=venki@google.com \
--cc=x86@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