From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Robin Getz <rgetz@blackfin.uclinux.org>,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
vapier.adi@gmail.com, lethal@linux-sh.org
Subject: Re: [RFC v2] kernel/printk.c - handling more than one CON_BOOT
Date: Wed, 1 Jul 2009 23:14:11 +0200 [thread overview]
Message-ID: <20090701211411.GD631@elte.hu> (raw)
In-Reply-To: <20090701140128.7924f3c4.akpm@linux-foundation.org>
* Andrew Morton <akpm@linux-foundation.org> wrote:
> > > I think it would be useful if we had a description of the new
> > > design, similar to your description of the "Today" behaviour
> > > above. Perhaps as a comment over register_console()?
> >
> > Can do - do you want it as v3 or on-top of this one?
>
> I'm easy either way. Ingo might have applied to one of his trees,
> in which case a replacement patch might cause him problems, dunno.
Not yet - i was waiting for feedback from you and Linus. Would be
nice to have a from-scratch v3 that adresses all the review
feedback.
Ingo
next prev parent reply other threads:[~2009-07-01 21:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 11:03 RFC - printk handling more than one CON_BOOT Robin Getz
2009-06-30 22:25 ` Ingo Molnar
2009-06-30 23:05 ` Robin Getz
2009-06-30 23:14 ` Ingo Molnar
2009-07-01 0:29 ` Robin Getz
2009-07-01 2:51 ` [RFC v2] kernel/printk.c - " Robin Getz
2009-07-01 19:44 ` Andrew Morton
2009-07-01 20:50 ` Robin Getz
2009-07-01 21:01 ` Andrew Morton
2009-07-01 21:14 ` Ingo Molnar [this message]
2009-07-01 21:28 ` Robin Getz
2009-07-01 21:31 ` Robin Getz
2009-07-02 1:08 ` [PATCH] - printk " Robin Getz
2009-07-03 8:58 ` [tip:core/printk] printk: Enable the use of more than one CON_BOOT (early console) tip-bot for Robin Getz
2009-07-21 18:37 ` [PATCH] - printk handling more than one CON_BOOT Robin Getz
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=20090701211411.GD631@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rgetz@blackfin.uclinux.org \
--cc=torvalds@linux-foundation.org \
--cc=vapier.adi@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.