From: Greg KH <greg@kroah.com>
To: "Kilau, Scott" <Scott_Kilau@digi.com>
Cc: germano.barreiro@cyclades.com, linux-kernel@vger.kernel.org
Subject: Re: patch for sysfs in the cyclades driver
Date: Wed, 3 Nov 2004 13:23:19 -0800 [thread overview]
Message-ID: <20041103212318.GA29830@kroah.com> (raw)
In-Reply-To: <71A17D6448EC0140B44BCEB8CD0DA36E04B9D81C@minimail.digi.com>
On Wed, Nov 03, 2004 at 02:20:39PM -0600, Kilau, Scott wrote:
> > > Maybe we can allow a "custom" name to be sent into the
> > > tty_register_device() call? Like add another option parameter
> called
> > > "custom_name" that if non-NULL, is used instead of the derived name?
>
> > Why? What would you call it that would be any different from what we
> > use today? I guess I don't understand why you don't like the kernel
> > names.
>
> > greg k-h
>
> Well, tty name compatibly reasons with a couple of our drivers.
>
> Most of our new Linux users for a couple of our older products are
> coming
> from a specific different OS who are adamant that we keep the tty names
> the way they were used to under that OS.
>
> Also, I can see some oddball products out there that might need
> only 1 tty out there.
>
> Instead of forcing "ttyoddball0" for the name, it would
> be nice to let the driver use "ttyoddball", or whatever it wanted.
Your driver can use whatever name you wanted, as long as it's the
LANNANA name that you asked for and were assigned. We do have standards
for a good reason, and the kernel will follow them.
That being said, have your customers use a tool like udev. Then they
can name their tty devices whatever they want. No limitations there at
all.
Hope this helps,
greg k-h
next prev parent reply other threads:[~2004-11-03 21:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 20:20 patch for sysfs in the cyclades driver Kilau, Scott
2004-11-03 21:23 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-04 17:50 Kilau, Scott
2004-11-04 18:28 ` Germano
2004-11-04 16:40 Kilau, Scott
2004-11-04 17:39 ` Greg KH
2004-11-03 22:35 Kilau, Scott
2004-11-03 23:08 ` Greg KH
2004-11-03 19:55 Kilau, Scott
2004-11-03 20:03 ` Greg KH
2004-11-03 13:09 Germano
2004-11-04 10:25 ` Marcelo Tosatti
2004-11-04 16:58 ` Roland Dreier
2004-11-04 14:29 ` Marcelo Tosatti
2004-11-04 17:40 ` Roland Dreier
2004-11-04 17:44 ` Greg KH
2004-11-04 17:42 ` Greg KH
2004-11-04 17:40 ` Greg KH
2004-11-04 19:05 ` Roland Dreier
2004-11-04 19:17 ` Greg KH
[not found] <71A17D6448EC0140B44BCEB8CD0DA36E04B9D812@minimail.digi.com>
2004-11-03 2:28 ` Greg KH
2004-10-28 18:56 Germano Barreiro
2004-10-30 4:40 ` Greg KH
2004-11-01 17:01 ` germano.barreiro
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=20041103212318.GA29830@kroah.com \
--to=greg@kroah.com \
--cc=Scott_Kilau@digi.com \
--cc=germano.barreiro@cyclades.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox