From: Takashi Iwai <tiwai@suse.de>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH 1/8] sound: use KERN_WARNING, not KERN_WARN
Date: Thu, 05 Nov 2009 09:10:50 +0100 [thread overview]
Message-ID: <s5hr5sdbddh.wl%tiwai@suse.de> (raw)
In-Reply-To: <1257379492822@xenotime.net>
At Wed, 04 Nov 2009 16:04:52 -0800,
Randy Dunlap wrote:
>
> From: Randy Dunlap <randy.dunlap@oracle.com>
> Subject: Use KERN_WARNING instead of KERN_WARN, which does not exist
>
> Reported-by: Andrew Lyon <andrew.lyon@gmail.com>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> Cc: Jaroslav Kysela <perex@perex.cz>
> Cc: Takashi Iwai <tiwai@suse.de>
Applied now. Thanks.
Takashi
> ---
> sound/oss/sb_common.c | 4 ++--
> sound/oss/sb_ess.c | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> --- lnx-2632-rc6.orig/sound/oss/sb_common.c
> +++ lnx-2632-rc6/sound/oss/sb_common.c
> @@ -157,7 +157,7 @@ static void sb_intr (sb_devc *devc)
> break;
>
> default:
> - /* printk(KERN_WARN "Sound Blaster: Unexpected interrupt\n"); */
> + /* printk(KERN_WARNING "Sound Blaster: Unexpected interrupt\n"); */
> ;
> }
> }
> @@ -177,7 +177,7 @@ static void sb_intr (sb_devc *devc)
> break;
>
> default:
> - /* printk(KERN_WARN "Sound Blaster: Unexpected interrupt\n"); */
> + /* printk(KERN_WARNING "Sound Blaster: Unexpected interrupt\n"); */
> ;
> }
> }
> --- lnx-2632-rc6.orig/sound/oss/sb_ess.c
> +++ lnx-2632-rc6/sound/oss/sb_ess.c
> @@ -782,7 +782,7 @@ printk(KERN_INFO "FKS: ess_handle_channe
> break;
>
> default:;
> - /* printk(KERN_WARN "ESS: Unexpected interrupt\n"); */
> + /* printk(KERN_WARNING "ESS: Unexpected interrupt\n"); */
> }
> }
>
>
>
> --
>
prev parent reply other threads:[~2009-11-05 8:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 0:04 [PATCH 1/8] sound: use KERN_WARNING, not KERN_WARN Randy Dunlap
2009-11-05 0:04 ` [PATCH 7/8] docs: serial/tty, add to ldisc methods Randy Dunlap
2009-11-05 0:16 ` Alan Cox
2009-11-05 0:04 ` [PATCH 6/8] docs: explain procs_running better Randy Dunlap
2009-11-05 0:04 ` [PATCH 3/8] docs: use DMA_BIT_MASK Randy Dunlap
2009-11-05 0:04 ` [PATCH 8/8] docs: use misc-devices/ dir for drivers Randy Dunlap
2009-11-05 0:04 ` [PATCH 2/8] docs: use KERN_WARNING, not KERN_WARN Randy Dunlap
2009-11-05 0:04 ` [PATCH 4/8] docbook: signal_pending has an argument Randy Dunlap
2009-11-05 8:10 ` Takashi Iwai [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=s5hr5sdbddh.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=rdunlap@xenotime.net \
/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