[lkml]   [2004]   [Jun]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH][2.6] fix bridge sysfs improperly initialised knobject
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.


greg k-h
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:03    [W:0.046 / U:4.084 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site