From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Andrew Morton <akpm@osdl.org>,
James Simmons <jsimmons@infradead.org>
Subject: Re: [PATCH] VT locking
Date: Wed, 07 Jan 2004 08:44:00 +1100 [thread overview]
Message-ID: <1073425440.773.10.camel@gaston> (raw)
In-Reply-To: <Pine.GSO.4.58.0401061725250.5752@waterleaf.sonytel.be>
>
> Looks like a nice opportunity to introduce an arch-specific printk() stub:
>
> void *arch_printk(const char *args);
>
> if (arch_printk)
> arch_printk(printk_buf);
Right... I admit I didn't even notice the printk_btext stuff leaked with
this patch, this is debug stuff that wasn't really supposed to get out
of my tree, oh well... I shouldn't do patches when I'm sick with +40°
fever...
Andrew, the only bits of the kernel/printk.c that are supposed to get
to your tree are related to is_console_locked() at this point. The
force_printk_to_btext is a debug tool that allow to route all printk's
to some early-boot output mecanism, though it would eventually be
acceptable upstream with Geert's idea of arch_printk...
Cheers,
Ben.
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
next prev parent reply other threads:[~2004-01-06 21:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 0:33 [PATCH] VT locking Benjamin Herrenschmidt
2004-01-06 12:16 ` Pavel Machek
2004-01-06 16:31 ` Geert Uytterhoeven
2004-01-06 21:44 ` Benjamin Herrenschmidt [this message]
2004-01-06 22:00 ` Andrew Morton
2004-01-06 23:08 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2004-01-06 0:17 Benjamin Herrenschmidt
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=1073425440.773.10.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).