From: Andrew Morton <akpm@osdl.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: geert@linux-m68k.org, linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net, jsimmons@infradead.org
Subject: Re: [PATCH] VT locking
Date: Tue, 6 Jan 2004 14:00:02 -0800 [thread overview]
Message-ID: <20040106140002.6806757b.akpm@osdl.org> (raw)
In-Reply-To: <1073425440.773.10.camel@gaston>
Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> 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...
That's OK, it's just in there for a soak-test at present - this stuff is
quite a long way away, yes?
It's probably just easiest for you to work against current -bk, send me a
single rolled up patch whenever you have new things for people to test.
When we're happy with it all we can do a bk merge of everything.
-------------------------------------------------------
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:58 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
2004-01-06 22:00 ` Andrew Morton [this message]
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=20040106140002.6806757b.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=benh@kernel.crashing.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).