From: Greg KH <greg@kroah.com>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: mochel@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: RFC: bus_type and device_class merge (or partial merge)
Date: Thu, 19 Dec 2002 15:37:01 -0800 [thread overview]
Message-ID: <20021219233701.GA8536@kroah.com> (raw)
In-Reply-To: <200212192244.OAA06433@adam.yggdrasil.com>
On Thu, Dec 19, 2002 at 02:44:53PM -0800, Adam J. Richter wrote:
> >> = Adam Richter
> > = Patrick Mochel
>
> >Especially during the continuing evolution
> >of the model. At least for now, and for probably a very long time, I will
> >not consider patches to consolidate the two object types.
>
> Linux will be better if we decide things by weighing technical
> benefits rather than by attempts at diktat. I recommend you keep an
> open mind about it.
Heh, if anyone has kept an open mind around here, it's Pat. Look at the
crap that the driver writers have forced him to accommodate. Here's a
small drawing that some people did at OLS 2002 to help get across how
all of the wide range of busses, classes, devices, and drivers interact
with just one kind of subsystem:
http://www.kroah.com/linux/images/driver_model_1_ols_2002.jpg
The existing code handles monstrosities like that quite well, because he
has kept an open mind, and listened to the driver and subsystem authors.
And yes, we need to start writing more class support, it's next on my
list too. Patches to do this would be greatly appreciated.
thanks,
greg k-h
next prev parent reply other threads:[~2002-12-19 23:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 19:36 RFC: bus_type and device_class merge (or partial merge) Adam J. Richter
2002-12-19 20:37 ` Patrick Mochel
2002-12-19 22:44 ` Adam J. Richter
2002-12-19 23:37 ` Greg KH [this message]
2002-12-20 4:29 ` Patrick Mochel
-- strict thread matches above, loose matches on Subject: below --
2002-12-21 9:00 Adam J. Richter
2002-12-21 10:43 Adam J. Richter
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=20021219233701.GA8536@kroah.com \
--to=greg@kroah.com \
--cc=adam@yggdrasil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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