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.0910221213160.21601@chino.kir.corp.google.com>
Date:	Thu, 22 Oct 2009 12:15:41 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Alex Chiang <achiang@...com>
cc:	Randy Dunlap <randy.dunlap@...cle.com>,
	Greg Kroah-Hartman <greg@...ah.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, Alex Chiang 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.
> 
> What do you think about keeping all the descriptions in the same
> file, sysfs-devices-system-cpu vs. splitting them out into
> separate files, sysfs-devices-system-cpu-topology, e.g.?
> 

That's fine since the directories don't contain an egregious amount of 
files that sysfs-devices-system-cpu becomes overly long.

I suggest spliting the individual files into their own sections within 
sysfs-devices-system-cpu, though, so they each have their own What, Date, 
KernelVersion, Contact, and Description fields.
--
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/