linux-kernel - Re: [PATCH 0/7] Documentation: document /sys/devices/system/cpu/

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.DEB.2.00.0910230228210.28109@chino.kir.corp.google.com>
Date:	Fri, 23 Oct 2009 02:28:27 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Greg KH <greg@...ah.com>
cc:	Alex Chiang <achiang@...com>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/7] Documentation: document /sys/devices/system/cpu/

On Thu, 22 Oct 2009, Greg KH wrote:

> > I know it's long, but I think some automated scripts are eventually going 
> > to use this documentation and it's best to follow the guidelines in 
> > Documentation/ABI/README.
> 
> They are?  I don't know of any such scripts anywhere, do you?
> 

I had assumed that there were guidelines for composing the ABI documents 
so that files could eventually be matched automatically with the 
documentation to provide insight into what it does.  The only thing I 
personally use is "grep ^What:.*file Documentation/ABI/*" to find if a 
sysfs file is documented and that's because I'm not interested in all 
occurrences, just the specific documentation of that file.
--
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/