From: Horms <horms@verge.net.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] [IA64]: add newline to PAL-code warning message
Date: Tue, 06 Feb 2007 03:14:45 +0000 [thread overview]
Message-ID: <20070206031445.GA12585@verge.net.au> (raw)
On Mon, Feb 05, 2007 at 01:18:16PM +0100, Gerald Pfeifer wrote:
> On Mon, 5 Feb 2007, Horms wrote:
> > Signed-off-by: Simon Horman <horms@verge.net.au>
> > - printk(KERN_WARNING "%s: no PAL-code memory-descriptor found",
> > + printk(KERN_WARNING "%s: no PAL-code memory-descriptor found\n",
> ^^
>
> This is usually referred to as newline, not return. Return, or
> carriage return, would be '\r' instead of '\n'.
Thanks, updated accordingly.
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
[IA64]: Add newline to PAL-code warning message
Signed-off-by: Simon Horman <horms@verge.net.au>
Index: linux-2.6/arch/ia64/kernel/efi.c
=================================--- linux-2.6.orig/arch/ia64/kernel/efi.c 2007-01-31 16:54:43.000000000 +0900
+++ linux-2.6/arch/ia64/kernel/efi.c 2007-01-31 16:54:46.000000000 +0900
@@ -380,7 +380,7 @@
#endif
return __va(md->phys_addr);
}
- printk(KERN_WARNING "%s: no PAL-code memory-descriptor found",
+ printk(KERN_WARNING "%s: no PAL-code memory-descriptor found\n",
__FUNCTION__);
return NULL;
}
reply other threads:[~2007-02-06 3:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070206031445.GA12585@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-ia64@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