From: gshan <gshan@alcatel-lucent.com>
To: linux-kernel@vger.kernel.org
Subject: It's a bug of printk?
Date: Thu, 03 May 2007 09:33:45 +0800 [thread overview]
Message-ID: <46393BF9.8090408@alcatel-lucent.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0705021756210.5342@asgard.lang.hm>
Hi,
I need 2 consoles for 2 individual serial ports that is registered by
register_console(). The console for the 1st serial port is registered at
first. I can see the output from the serial port #1 before the console
for the 2nd serial port is registered. However, I saw duplicated output
from serial port #1 again after the console for #2 serial port is
registered.
The root cause is that there is only one con_start for all consoles. I
think con_start need to be merged with struct console so that different
console could have different start?
Thanks,
Gavin
next prev parent reply other threads:[~2007-05-03 1:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f058a9c30705021214k75da330ai4d79a2b6b2806652@mail.gmail.com>
2007-05-02 19:18 ` FEATURE REQUEST: merge MD software raid and LVM in one unique layer Miguel Sousa Filipe
2007-05-02 20:10 ` Diego Calleja
2007-05-02 20:51 ` Miguel Sousa Filipe
2007-05-03 0:58 ` david
2007-05-03 1:33 ` gshan [this message]
2007-05-03 8:08 ` David Greaves
2007-05-03 9:25 ` Miguel Sousa Filipe
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=46393BF9.8090408@alcatel-lucent.com \
--to=gshan@alcatel-lucent.com \
--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 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.