linux-kernel - Re: Generic kernel features that need architecture(mips) support

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150611062452.GB32133@gmail.com>
Date:	Thu, 11 Jun 2015 08:24:53 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Xose Vazquez Perez <xose.vazquez@...il.com>,
	Jonathan Corbet <corbet@....net>
Cc:	Ralf Baechle <ralf@...ux-mips.org>, linux-mips@...ux-mips.org,
	linux-arch@...r.kernel.org, linux-api@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Generic kernel features that need architecture(mips) support

(Jon Cc:-ed)

* Xose Vazquez Perez <xose.vazquez@...il.com> wrote:

> On 06/10/2015 04:58 PM, Ralf Baechle wrote:
> 
> > How are the documentation files in Documentation/features/ maintained?
> > They were automatically generated so I wonder if I have to take care
> > of anything.
> 
> CC: Ingo and related ml.

So changes to Documentation/features/ should come as simple patches done from hand 
editing, there's no need to preserve any initial (half-)automated generation. 
Formatting should be preserved so that Documentation/features/list-arch.sh still 
works as before.

Jon: would you like to receive all patches to Documentation/features/ so you can 
collect them in the documentation tree, or can maintainers patch it as part of any 
feature work that affects the tables? I think it's all finegrained enough to not 
create conflicts. That way they would become partly self-maintaining. (Or at least 
one can always hope! ;-)

Thanks,

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