* [PATCH] [IA64]: add return to PAL-code warning message
@ 2007-02-05 1:17 Horms
2007-02-05 12:18 ` Gerald Pfeifer
0 siblings, 1 reply; 2+ messages in thread
From: Horms @ 2007-02-05 1:17 UTC (permalink / raw)
To: linux-ia64
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;
}
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] [IA64]: add return to PAL-code warning message
2007-02-05 1:17 [PATCH] [IA64]: add return to PAL-code warning message Horms
@ 2007-02-05 12:18 ` Gerald Pfeifer
0 siblings, 0 replies; 2+ messages in thread
From: Gerald Pfeifer @ 2007-02-05 12:18 UTC (permalink / raw)
To: linux-ia64
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'.
Gerald
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-02-05 12:18 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-02-05 1:17 [PATCH] [IA64]: add return to PAL-code warning message Horms
2007-02-05 12:18 ` Gerald Pfeifer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox