From: Simon Horman <horms@verge.net.au>
To: Rich Felker <dalias@libc.org>
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
"D. Jeff Dionne" <jeff@uClinux.org>,
Rob Landley <rob@landley.net>
Subject: Re: [PATCH 2/2] MAINTAINERS: remove linux-sh list from non-arch/sh sections
Date: Fri, 08 Jan 2016 06:56:46 +0000 [thread overview]
Message-ID: <20160108065642.GA1215@verge.net.au> (raw)
In-Reply-To: <20160108044054.GA7130@brightrain.aerifal.cx>
On Thu, Jan 07, 2016 at 11:40:54PM -0500, Rich Felker wrote:
> From: Rich Felker <dalias@libc.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@vger.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.
next prev parent reply other threads:[~2016-01-08 6:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 4:39 [PATCH 0/2] Resume maintenance & development of arch/sh Rich Felker
2016-01-08 4:39 ` [PATCH 1/2] MAINTAINERS: return arch/sh to maintained state, with new maintainers Rich Felker
2016-01-11 17:53 ` Peter Zijlstra
2016-01-13 1:40 ` Simon Horman
2016-01-15 0:52 ` Rich Felker
2016-01-15 9:31 ` Geert Uytterhoeven
2016-01-17 2:32 ` Rich Felker
2016-01-17 8:48 ` Geert Uytterhoeven
2016-01-08 4:40 ` [PATCH 2/2] MAINTAINERS: remove linux-sh list from non-arch/sh sections Rich Felker
2016-01-08 6:56 ` Simon Horman [this message]
2016-01-08 9:01 ` Geert Uytterhoeven
2016-01-08 18:21 ` Rich Felker
2016-01-08 20:35 ` Geert Uytterhoeven
2016-01-08 20:52 ` Rich Felker
2016-01-10 19:41 ` Geert Uytterhoeven
2016-01-08 17:35 ` Rob Landley
2016-01-08 18:28 ` Laurent Pinchart
2016-01-08 19:40 ` Rich Felker
2016-01-08 23:15 ` Laurent Pinchart
2016-01-08 22:50 ` Rob Landley
2016-01-10 20:05 ` Geert Uytterhoeven
2016-01-11 2:02 ` Rob Landley
2016-01-11 2:22 ` uClinux.org
2016-01-08 18:51 ` Rich Felker
2016-01-08 18:03 ` Sergei Shtylyov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160108065642.GA1215@verge.net.au \
--to=horms@verge.net.au \
--cc=akpm@linux-foundation.org \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=jeff@uClinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rob@landley.net \
--cc=ysato@users.sourceforge.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).