From: Andrew Morton <akpm@linux-foundation.org>
To: Feng Tang <feng.tang@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"gregkh@suse.de" <gregkh@suse.de>,
"alan@linux.intel.com" <alan@linux.intel.com>
Subject: Re: [PATCH] console: prevent registered consoles from dumping old kernel message over again
Date: Wed, 19 Jan 2011 17:51:34 -0800 [thread overview]
Message-ID: <20110119175134.5a2f283f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20110120094458.144708e0@feng-i7>
On Thu, 20 Jan 2011 09:44:58 +0800
Feng Tang <feng.tang@intel.com> wrote:
> > How's about something like this?
>
> Yes, it makes sense, I should add some check. And this new
> "exclusive_console" should be better as its name shows what it is for.
Is it racy, or does console_sem coverage save us?
Anyway. If you think that the exclusive_console approach is suitable,
please send a tested patch back at me sometime?
next prev parent reply other threads:[~2011-01-20 1:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 6:48 Feng Tang
2011-01-12 11:14 ` Alan Cox
2011-01-12 14:51 ` Feng Tang
2011-01-12 14:50 ` Alan Cox
2011-01-20 0:11 ` Andrew Morton
2011-01-20 1:44 ` Feng Tang
2011-01-20 1:51 ` Andrew Morton [this message]
2011-01-20 2:31 ` Feng Tang
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=20110119175134.5a2f283f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=feng.tang@intel.com \
--cc=gregkh@suse.de \
--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
Powered by JetHome