From: Greg KH <greg@kroah.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Zwane Mwaikambo <zwane@fsmlabs.com>,
"David S. Miller" <davem@redhat.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.6] fix bridge sysfs improperly initialised knobject
Date: Thu, 17 Jun 2004 13:58:25 -0700 [thread overview]
Message-ID: <20040617205825.GB3138@kroah.com> (raw)
In-Reply-To: <20040617134636.216f430e@dell_ss3.pdx.osdl.net>
On Thu, Jun 17, 2004 at 01:46:36PM -0700, Stephen Hemminger wrote:
> Yes, this would get rid of the name, but then wouldn't bridge show up
> as top level subsystem /sys/bridge.
If you register it, yes it would. Hm, what happens if you don't
register it...
> Is there no way to register without causing bogus hotplug events?
You are wanting to prevent hotplug events for a subset of a subsystem's
devices, right? You faked out the core by providing a fake subsystem.
How about just using the filter of the subsystem you really want these
entries to show up under? Would that work?
> I am getting a bad taste about the whole sysfs programming model, since
> it seems like programming by side effect. it would be better for sysfs
> to handle the case of hidden subsystems, or provide an alternate way
> not to generate hotplug events.
Well, we never considered that you would want to nest subsystems in such
a wierd way :)
Anyway, take a look at the filter ability to see if that would work out
for you instead of having to create a new subsystem.
thanks,
greg k-h
next prev parent reply other threads:[~2004-06-17 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 23:48 Zwane Mwaikambo
2004-06-17 20:46 ` Stephen Hemminger
2004-06-17 20:51 ` David S. Miller
2004-06-17 20:58 ` Greg KH [this message]
2004-06-17 21:45 ` Stephen Hemminger
2004-06-18 20:19 ` David S. Miller
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=20040617205825.GB3138@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=zwane@fsmlabs.com \
/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
all inboxes | Powered by JetHome®