From: Jeff Garzik <jgarzik@pobox.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Greg KH <greg@kroah.com>, Alan Stern <stern@rowland.harvard.edu>,
Kernel development list <linux-kernel@vger.kernel.org>,
Patrick Mochel <mochel@digitalimplant.org>
Subject: Re: "Miscellaneous" bus for the driver model?
Date: Wed, 07 Jan 2004 16:20:43 -0500 [thread overview]
Message-ID: <3FFC782B.1060307@pobox.com> (raw)
In-Reply-To: <20040107211656.D18708@flint.arm.linux.org.uk>
Russell King wrote:
> On Wed, Jan 07, 2004 at 09:33:45AM -0800, Greg KH wrote:
>
>>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.
>
>
> Can we get this patch merged ASAP please? It should really have gone
> in before 2.6 so we don't have this change during a stable kernel series.
It's already in :)
Jeff
ChangeSet@1.1474.51.99, 2003-12-29 21:54:21-08:00, akpm@osdl.org
[PATCH] Rename legacy_bus to platform_bus
From: Jeff Garzik <jgarzik@pobox.com>
I've seen this patch floating around. Not sure the origin, but it's
surfaced on lkml and also when I was poking around handhelds.org CVS for
iPAQ patches: on non-PCs, particularly system-on-chip devices but not
just there, you have a custom "platform bus" that is the root of pretty
much all other devices and buses.
It's something I wanted to make sure people didn't forget; to make sure
the legacy_bus didn't get "legacied out of existence." ;-)
prev parent reply other threads:[~2004-01-07 21:21 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
2004-01-07 21:16 ` Russell King
2004-01-07 21:20 ` Jeff Garzik [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=3FFC782B.1060307@pobox.com \
--to=jgarzik@pobox.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=rmk+lkml@arm.linux.org.uk \
--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).