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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20150611072028.7d0fe2d7@lwn.net>
Date:	Thu, 11 Jun 2015 07:20:28 -0600
From:	Jonathan Corbet <corbet@....net>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Xose Vazquez Perez <xose.vazquez@...il.com>,
	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

On Thu, 11 Jun 2015 08:24:53 +0200
Ingo Molnar <mingo@...nel.org> wrote:

> 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! ;-)

I sort of figured I'd handle it the way I do the rest of Documentation/ —
I'm happy to herd the patches, but I also have no problem staying out of
the way when other maintainers reach into it.

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