From: Greg KH <greg@kroah.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Kernel development list <linux-kernel@vger.kernel.org>,
Patrick Mochel <mochel@digitalimplant.org>
Subject: Re: "Miscellaneous" bus for the driver model?
Date: Wed, 7 Jan 2004 09:33:45 -0800 [thread overview]
Message-ID: <20040107173345.GD31177@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0401071054220.850-100000@ida.rowland.org>
On Wed, Jan 07, 2004 at 11:00:16AM -0500, Alan Stern wrote:
> Would it make sense for the driver model core to add a "miscellaneous" or
> "other" bus, intended for devices or drivers that are one-of-a-kind or
> otherwise non-standard? Kind of similar to the platform bus but meant
> for new things, not part of a legacy or other system/architecture-specific
> base?
That's what the "legacy" bus is for. There's a patch floating around
that renames that bus to "platform" to remove any connotation that
"legacy" might occur.
Hope this helps,
greg k-h
next prev parent reply other threads:[~2004-01-07 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 16:00 "Miscellaneous" bus for the driver model? Alan Stern
2004-01-07 17:33 ` Greg KH [this message]
2004-01-07 21:16 ` Russell King
2004-01-07 21:20 ` Jeff Garzik
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=20040107173345.GD31177@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=stern@rowland.harvard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).