From: "Teras Timo (EXT-YomiGroup/Helsinki)" <Ext-Timo.Teras@nokia.com>
To: ext Stephen Hemminger <shemminger@osdl.org>
Cc: ext ext Christoph Hellwig <hch@infradead.org>,
davem@davemloft.net, netdev@oss.sgi.com
Subject: Re: [PATCH] Add ability to register class interfaces for network class
Date: Wed, 27 Oct 2004 21:38:04 +0300 [thread overview]
Message-ID: <20041027183804.GA12585@two.research.nokia.com> (raw)
In-Reply-To: <20041027085906.665d0125@guest-251-240.pdx.osdl.net>
On Wed, Oct 27, 2004 at 08:59:06AM -0700, ext Stephen Hemminger wrote:
> The Ethernet bridge code creates attribute groups in several places
> without additional interfaces. How hard is it to do:
>
> int br_sysfs_addbr(struct net_device *dev)
> {
> struct kobject *brobj = &dev->class_dev.kobj;
> struct net_bridge *br = netdev_priv(dev);
> int err;
>
> err = sysfs_create_group(brobj, &bridge_group);
> if (err) {
> pr_info("%s: can't create group %s/%s\n",
> __FUNCTION__, dev->name, bridge_group.name);
> goto out1;
> }
This way the problem is that I have to know which devices I will
add the attributes. But the point is to add attributes to
all netdevs.
Using this approach I'd have to enumerate all the interfaces every
now and then.
If I have my class interface I get a callback whenever an
interface is created or deleted and I can automatically add the
attribute to all netdevs.
Cheers,
Timo
next prev parent reply other threads:[~2004-10-27 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 18:35 [PATCH] Add ability to register class interfaces for network class Timo Teräs
2004-10-26 18:48 ` Christoph Hellwig
2004-10-26 20:52 ` Teras Timo (EXT-YomiGroup/Helsinki)
2004-10-27 11:13 ` ext Christoph Hellwig
2004-10-27 11:31 ` Timo Teräs
2004-10-27 15:59 ` Stephen Hemminger
2004-10-27 18:38 ` Teras Timo (EXT-YomiGroup/Helsinki) [this message]
2004-10-27 18:55 ` Stephen Hemminger
2004-10-27 19:20 ` Teras Timo (EXT-YomiGroup/Helsinki)
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=20041027183804.GA12585@two.research.nokia.com \
--to=ext-timo.teras@nokia.com \
--cc=davem@davemloft.net \
--cc=hch@infradead.org \
--cc=netdev@oss.sgi.com \
--cc=shemminger@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;
as well as URLs for NNTP newsgroup(s).