public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH 0/2] Couple of I2O sysfs changes
@ 2005-09-13  4:31 Dmitry Torokhov
  2005-09-13  4:34 ` [PATCH 1/2] I2O: remove i2o_device_class_interface Dmitry Torokhov
  2005-09-13 10:33 ` [PATCH 0/2] Couple of I2O sysfs changes Markus Lidel
  0 siblings, 2 replies; 5+ messages in thread
From: Dmitry Torokhov @ 2005-09-13  4:31 UTC (permalink / raw)
  To: markus.lidel; +Cc: LKML

Hi Markus,

I was looking at the users of class_interfaces and stumbled across
I2O subsystem. As far as I understand the purpose of class interfaces
was to provide different 'views' on the hardware, not just to have
a callback to finish initialization of sysfs structures. I think it
woudl be better to remove i2o_device_class_interface and create
user/parent links right after class device registration.

Also, it looks like i2o_device_class itself is not needed - correct
me if I am wrong, but all i2o devics reside on their own bus so
i2o_devices class simply mirrors iformation from the bus and can
also be safely removed.

Please consider applying the 2 pathes below (just compile-tested,
don't have proper hardware).

-- 
Dmitry

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2005-09-13 19:07 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-09-13  4:31 [PATCH 0/2] Couple of I2O sysfs changes Dmitry Torokhov
2005-09-13  4:34 ` [PATCH 1/2] I2O: remove i2o_device_class_interface Dmitry Torokhov
2005-09-13  4:34   ` [PATCH 1/2] I2O: remove i2o_device_class Dmitry Torokhov
2005-09-13 10:33 ` [PATCH 0/2] Couple of I2O sysfs changes Markus Lidel
2005-09-13 19:06   ` Dmitry Torokhov

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox