linux-kernel - Re: [patch 00/04] RFC: Staging tree (drivers/staging)

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]

Date:	Fri, 26 Sep 2008 16:47:33 -0400
From:	"Parag Warudkar" <parag.lkml@...il.com>
To:	"Stefan Richter" <stefanr@...6.in-berlin.de>
Cc:	"Greg KH" <gregkh@...e.de>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	"Andreas Gruenbacher" <agruen@...e.de>,
	"Jeff Mahoney" <jeffm@...e.de>
Subject: Re: [patch 00/04] RFC: Staging tree (drivers/staging)

On Fri, Sep 26, 2008 at 4:39 PM, Stefan Richter
<stefanr@...6.in-berlin.de> wrote:
> Parag Warudkar wrote:
>>
>> Just name the staging modules with _stg prefix like I said - easier to
>> spot _stg in the module list than decoding the taint.
>
> ...
>>
>> It is nice to not have to change core kernel code and annoy users with
>> warnings
>
> Yes, let's annoy them with weird name changes instead.

So people now a days crave for documenting staging modules and also
get confused by the mixed use of driver_stg or driver? Come on.

The name changes hardly matter for auto loading staging modules and I
would be surprised if people document crap modules especially since
the stable ones are documented later if at all they end up being
documented.

Parag
--
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/