linux-kernel - Re: Where to put adapters

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] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0802192031350.26109@fbirervta.pbzchgretzou.qr>
Date:	Tue, 19 Feb 2008 20:37:18 +0100 (CET)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Karl Dahlke <eklhad@...cast.net>
cc:	linux-kernel@...r.kernel.org
Subject: Re: Where to put adapters


On Feb 19 2008 08:01, Karl Dahlke wrote:
>
>Now that notifiers are in, (yay!), people are going to start writing adapters
>for visually and motor impaired individuals.
>I suggest we place them in drivers/adapters in the source tree,

Umph, that sounds a bit generic. Network cards are sometimes referred
to as "network [card] adapter" and graphic cards to as "graphics adapter",
so by your suggestions, they would all go into drivers/adapters/.

When such a driver actually comes along, we can revisit the topic.

>and I suggest they put their virtual files in the directory /proc/adapters,
>which would be created via fs/proc/root.c as part of the /proc file system.

Please not. Either character-based devices or sysfs files, depending
on which flies best. Adapters are not really proc-related.
--
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/