From: Greg KH <greg@kroah.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] change netdevice to use struct device instead of struct class_device
Date: Thu, 6 Jul 2006 17:02:33 -0700 [thread overview]
Message-ID: <20060707000233.GA13921@kroah.com> (raw)
In-Reply-To: <1152109763.4260.19.camel@localhost>
On Wed, Jul 05, 2006 at 04:29:23PM +0200, Marcel Holtmann wrote:
> Hi Greg,
>
> > The patch needs some other changes to the driver core that are also in
> > my git tree, and included in the -mm release. Specifically these
> > patches are needed:
> > http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/driver/device-groups.patch
> > http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/driver/device-class-parent.patch
>
> while converting the Bluetooth subsystem from class devices to real
> devices, I had some similar situation with devices without parent. I
> actually used a Bluetooth platform device as parent for virtual or
> serial based devices.
The problem with that is you get a bunch of symlinks to that parent
device that you really don't want to have, when we have a device that is
associated with a class.
I was thinking of creating a /sys/devices/virtual/ to put these
unassociated devices into, and I'll play around with that a bit. I
don't know if we will hit some namespace issues with all of the
different devices that aren't associated with a "real" device if we lump
them all together into one directory...
thanks,
greg k-h
prev parent reply other threads:[~2006-07-07 0:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 22:47 [RFC] change netdevice to use struct device instead of struct class_device Greg KH
2006-07-03 23:07 ` Jeff Garzik
2006-07-03 23:16 ` Greg KH
2006-07-04 1:57 ` David Miller
2006-07-04 22:31 ` Greg KH
2006-07-05 18:29 ` David Miller
2006-07-05 14:29 ` Marcel Holtmann
2006-07-07 0:02 ` Greg KH [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=20060707000233.GA13921@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).