All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Stuart MacDonald <stuartm@connecttech.com>,
	tytso@mit.edu, linux-kernel@vger.kernel.org
Subject: Re: Fw: [Patch] Some updates to serial-5.05
Date: Wed, 14 Nov 2001 19:25:17 -0500	[thread overview]
Message-ID: <3BF30B6D.F42FEAB2@mandrakesoft.com> (raw)
In-Reply-To: <00df01c16d23$b409ab20$294b82ce@connecttech.com> <20011115001016.C19575@flint.arm.linux.org.uk>

Russell King wrote:
> I don't actually printk() the serial ports that have been discovered at
> boot time in the new serial CVS.  If people scream enough, I could be
> persuaded.  I'm currently of the opinion that they're noise, and if
> we're really interested in them, we've got a userspace tool to do it
> for us: setserial -bg /dev/ttyS*

I'll complain ;-)   It seems pretty standard for a driver to print out
at least one single line for each "interface" it registers; interface in
this case being ttySn.  IDE and SCSI layers print out hdX, ethernet
drivers print out ethX; serial should printk ttySx.

	Jeff


-- 
Jeff Garzik      | Only so many songs can be sung
Building 1024    | with two lips, two lungs, and one tongue.
MandrakeSoft     |         - nomeansno


  reply	other threads:[~2001-11-15  0:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-14 15:47 Fw: [Patch] Some updates to serial-5.05 Stuart MacDonald
2001-11-14 15:57 ` Jeff Garzik
2001-11-14 16:30   ` Stuart MacDonald
2001-11-14 16:35     ` Jeff Garzik
2001-11-14 18:46       ` Stuart MacDonald
2001-11-14 18:57         ` Jeff Garzik
2001-11-14 19:24           ` Stuart MacDonald
2001-11-14 17:04 ` Roman Kurakin
2001-11-15  0:10 ` Russell King
2001-11-15  0:25   ` Jeff Garzik [this message]
2001-11-15 15:23   ` Stuart MacDonald

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=3BF30B6D.F42FEAB2@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=stuartm@connecttech.com \
    --cc=tytso@mit.edu \
    /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.