From: Greg KH <greg@kroah.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC] change netdevice to use struct device instead of struct class_device
Date: Mon, 3 Jul 2006 16:16:10 -0700 [thread overview]
Message-ID: <20060703231610.GA18352@kroah.com> (raw)
In-Reply-To: <44A9A345.8040706@garzik.org>
On Mon, Jul 03, 2006 at 07:07:49PM -0400, Jeff Garzik wrote:
> Greg KH wrote:
> >I have a patch here that converts the network device structure to use
> >the struct device instead of struct class_device structure. It's a bit
> >too big to post here, so it's at:
> > http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/network-class_device-to-device.patch
>
> So.... this is a userspace ABI change, then?
No, not really. According to Documentation/ABI/testing/sysfs-class all
code that uses /sys/class/foo/ needs to be able to handle the fact that
those entries might be symlinks and not just directories. Everything
that I know of already works properly because the input layer has had
symlinks in /sys/class/input for quite some time now.
Do you know of any tools that use /sys/class/net/ that can not handle
symlinks there? I've been running this on my boxes for about a week now
with no noticeable issues. Renaming interfaces works just fine too.
thanks,
greg k-h
next prev parent reply other threads:[~2006-07-03 23:19 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 [this message]
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
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=20060703231610.GA18352@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.