linux-kernel - Re: [git patches] libata updates

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: <alpine.LFD.1.10.0805060919410.32269@woody.linux-foundation.org>
Date:	Tue, 6 May 2008 09:23:26 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Jeff Garzik <jeff@...zik.org>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-ide@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git patches] libata updates

On Tue, 6 May 2008, Jeff Garzik wrote:
>  
> +config PATA_SCH
> +	tristate "Intel SCH PATA support"
> +	depends on PCI
> +	help
> +	  This option enables support for Intel SCH PATA on the Intel
> +	  SCH (US15W, US15L, UL11L) series host controllers.
> +
> +	  If unsure, say N.

I think it would generally be good if people explained their drivers 
better than this.

If you know what the hell an SCH is, you don't *need* that help message in 
the first place! Agreed?

IOW, when adding drivers, please add help messages that actually explain 
what the driver is from a *user* perspective, not from a chip designer 
perspective. In this case, something like

	The Intel SCH chipset is the new low-power, small-footprint 
	embedded chipset that is generally paired with the Atom CPU and is 
	not their normal PC chipset.

or something. So that people can actually make a somewhat informed guess 
about whether it's relevant to them or not.

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