linux-kernel - Re: [PATCH 26/47] Driver core: add groups support to struct device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <d120d5000609260620me5cf24bw83fc6d65fa7cb232@mail.gmail.com>
Date:	Tue, 26 Sep 2006 09:20:17 -0400
From:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
To:	"Greg KH" <greg@...ah.com>
Cc:	linux-kernel@...r.kernel.org, "Linus Torvalds" <torvalds@...l.org>,
	"Andrew Morton" <akpm@...l.org>
Subject: Re: [PATCH 26/47] Driver core: add groups support to struct device

On 9/26/06, Greg KH <greg@...ah.com> wrote:
> From: Greg Kroah-Hartman <gregkh@...e.de>
>
> This is needed for the network class devices in order to be able to
> convert over to use struct device.
>

Greg,

You keep pushing out patches that merge class devices and standard
devices but you still have not shown the usefullness of this process.
Why do you feel the need to change internal kernel structures
(ever-expanding struct device to accomodate everything that is in
struct class_device) when it should be possible to simply adjust sysfs
representation of the kernel tree (moving class devices into
/sys/device/.. part of the tree)  to udev's liking and leave the rest
of the kernel alone. You have seen the patch, only minor changes in
driver/base/class.c are needed to accomplish the move.

I really disappointed that there was no discussion/review of the
implementation at all.

-- 
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/