From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: David VomLehn <dvomlehn@cisco.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
linux-usb@vger.kernel.org, greg@kroah.com,
linux-scsi@vger.kernel.org, netdev@vger.kernel.org,
arjan@infradead.org
Subject: Re: [PATCH 3/7] initdev:kernel:Await console discovery, v6
Date: Sat, 06 Jun 2009 10:55:09 +0200 [thread overview]
Message-ID: <4A2A2EED.3060506@s5r6.in-berlin.de> (raw)
In-Reply-To: <20090606023407.GA5695@cuplxvomd02.corp.sa.net>
David VomLehn wrote:
> Wait for the console device to become available.
>
> History
> v6 Changed BOOTDEV_* to INITDEV_*.
> v5.1 Corrected call to initdev_register() to be initdev_registered().
> v5 Change bootdev_* to initdev_*.
> v4 Use new hotplug synchronization infrastructure. Include Braille
> console support.
> v3.2 Use only a single new command line parameter by adding the possible
> value "forever". Add message specifying the parameter to modify to
> increase the delay for console initialization
> v3.1 Correct the abbreviation for milliseconds in
> Documentation/kernel-parameters.txt to be "ms", not "mS". Thanks to
> Peter Anvin for this.
> v3 Increase the default delay to 1 second and add kernel command line
> parameters to override the default delay. Thanks to David Brownell for
> his helpful suggestions.
> v2 Wait for the preferred console rather than any console. Make the
> delay interval a tunable.
> v1 Initial version
>
> Signed-off-by: David VomLehn <dvomlehn@cisco.com>
> ---
> drivers/accessibility/braille/braille_console.c | 2 +
> kernel/printk.c | 29 ++++++++++++++++++++++-
> 2 files changed, 30 insertions(+), 1 deletions(-)
Is this diff complete?
--
Stefan Richter
-=====-==--= -==- --==-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2009-06-06 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 2:34 David VomLehn
2009-06-06 8:55 ` Stefan Richter [this message]
2009-06-08 22:13 ` David VomLehn
2009-06-08 22:30 ` Stefan Richter
2009-06-08 22:34 ` David VomLehn
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=4A2A2EED.3060506@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=dvomlehn@cisco.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@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
all inboxes | Powered by JetHome®