mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Lyon <andrew.lyon@gmail.com>
Subject: Re: [PATCH 1/6 for 2.6.33] docs: use KERN_WARNING, not KERN_WARN
Date: Sun, 06 Dec 2009 20:09:47 -0800	[thread overview]
Message-ID: <1260158987.11126.141.camel@Joe-Laptop.home> (raw)
In-Reply-To: <12601530442994@xenotime.net>

On Sun, 2009-12-06 at 18:30 -0800, Randy Dunlap wrote:
> Subject: Use KERN_WARNING instead of KERN_WARN, which does not exist

Perhaps it's better to use pr_warning instead.



      parent reply	other threads:[~2009-12-07  4:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07  2:30 Randy Dunlap
2009-12-07  2:30 ` [PATCH 3/6] docs: fix signal_pending argument Randy Dunlap
2009-12-07  2:30 ` [PATCH 2/6] docs: use DMA_BIT_MASK instead of inline constant Randy Dunlap
2009-12-07  2:30 ` [PATCH 6/6] docs: use misc-devices/ dir for drivers Randy Dunlap
2009-12-07  2:30 ` [PATCH 5/6] docs: better explanation of procs_running Randy Dunlap
2009-12-07  4:09 ` 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=1260158987.11126.141.camel@Joe-Laptop.home \
    --to=joe@perches.com \
    --cc=andrew.lyon@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --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

all inboxes | Powered by JetHome®