mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David VomLehn <dvomlehn@cisco.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
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: Mon, 8 Jun 2009 15:34:06 -0700	[thread overview]
Message-ID: <20090608223406.GD22222@cuplxvomd02.corp.sa.net> (raw)
In-Reply-To: <4A2D90EB.4070005@s5r6.in-berlin.de>

On Tue, Jun 09, 2009 at 12:30:03AM +0200, Stefan Richter wrote:
> David VomLehn wrote:
>> On Sat, Jun 06, 2009 at 04:55:09AM -0400, Stefan Richter wrote:
>>> David VomLehn wrote:
> ...
>>>> 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
> ...
>>>> ---
>>>>  drivers/accessibility/braille/braille_console.c |    2 +
>>>>  kernel/printk.c                                 |   29 ++++++++++++++++++++++-
>>>>  2 files changed, 30 insertions(+), 1 deletions(-)
>>> Is this diff complete?
>>
>> To the best of my knowledge, yes, it is complete. What makes it look as though
>> it might not be?
>
> The history notes.
> kernel-parameters.txt, new command line parameter...

Now I understand--you haven't been following this in detail, and there is
no reason why you should have. The history reflects the fact that the
original approach changed completely once Alan Stern let me know that we
really could tell when we have discovered all attached USB devices. It's
still trying to solve the same problem, however, so I kept the history
for continuity.

> Stefan Richter

      reply	other threads:[~2009-06-08 22:34 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
2009-06-08 22:13   ` David VomLehn
2009-06-08 22:30     ` Stefan Richter
2009-06-08 22:34       ` David VomLehn [this message]

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=20090608223406.GD22222@cuplxvomd02.corp.sa.net \
    --to=dvomlehn@cisco.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --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 \
    --cc=stefanr@s5r6.in-berlin.de \
    /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®