linux-kernel - Re: [PATCH 2/2] MAINTAINERS: remove linux-sh list from non-arch/sh sections

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]

Date:	Fri, 8 Jan 2016 15:56:46 +0900
From:	Simon Horman <horms@...ge.net.au>
To:	Rich Felker <dalias@...c.org>
Cc:	linux-sh@...r.kernel.org, linux-kernel@...r.kernel.org,
	Yoshinori Sato <ysato@...rs.sourceforge.jp>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>,
	"D. Jeff Dionne" <jeff@...inux.org>, Rob Landley <rob@...dley.net>
Subject: Re: [PATCH 2/2] MAINTAINERS: remove linux-sh list from non-arch/sh
 sections

On Thu, Jan 07, 2016 at 11:40:54PM -0500, Rich Felker wrote:
> From: Rich Felker <dalias@...c.org>
> 
> Recently the bulk of traffic on the linux-sh list has been unrelated
> to arch/sh but instead focused on Renesas hardware for their ARM-based
> SoCs. As part of resuming maintenance of arch/sh, remove the linux-sh
> list from the MAINTAINERS file sections for these other components so
> that new arch/sh development is not drowned out by unrelated
> cross-postings.

The use of the linux-sh mailing list has evolved somewhat over time,
from SH related to ARM related. Its name (obviously) has not evolved.

Dropping linux-sh@...r.kernel.org from portions of the MAINTAINERS file as
you suggest would essentially leave the Renesas ARM work without a mailing
list or patchwork instance. Both of which are actively used for that work.

Off-hand I can think of three solutions to this problem:

1. Live with the noise
2. Establish a new list (and possibly patchwork instance) for the SH work.
3. Establish a new list and patchwork instance for the ARM work.