From: Geert Uytterhoeven <geert@linux-m68k.org> To: Simon Horman <horms@verge.net.au> Cc: Rich Felker <dalias@libc.org>, Linux-sh list <linux-sh@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, Yoshinori Sato <ysato@users.sourceforge.jp>, 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 09:01:25 +0000 [thread overview] Message-ID: <CAMuHMdXkK68wM0D2-auNskSDv2ni6R4GabA90We8PbYXikO9Pw@mail.gmail.com> (raw) In-Reply-To: <20160108065642.GA1215@verge.net.au> First, I'd like to welcome the adoption of the arch/sh/ architecture. On Fri, Jan 8, 2016 at 7:56 AM, Simon Horman <horms@verge.net.au> wrote: > 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. Indeed, following the evolution of the SoC hardware, cfr. below. It meaning has shifted more to the "Linux Renesas mailing list". > 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. Personally, I'd go for option 1. I would even like to propose H8/300 to join, as they share IP cores, too (m32r doesn't, AFAIK). Many old ARM/SH-Mobile SoCs look like SH SoCs with an ARM CPU core bolted on. Recent Renesas ARM SoCs still share many IP cores with older SH SoCs; most of them even have a secondary SH4 CPU core. Using the SH4 CPU core could be useful for doing SH4 work, until J4 becomes mainstream (cfr. old prototype in http://www.spinics.net/lists/linux-sh/msg07188.html). Probably the Jx series won't share IP cores with SH/ARM, but as arch/sh/ maintainers you have to care about older Renesas SH platforms, too. For patchwork, that would mean some more delegation needs to be put in place. So far my 0.05€... Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert@linux-m68k.org> To: Simon Horman <horms@verge.net.au> Cc: Rich Felker <dalias@libc.org>, Linux-sh list <linux-sh@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, Yoshinori Sato <ysato@users.sourceforge.jp>, 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, 8 Jan 2016 10:01:25 +0100 [thread overview] Message-ID: <CAMuHMdXkK68wM0D2-auNskSDv2ni6R4GabA90We8PbYXikO9Pw@mail.gmail.com> (raw) In-Reply-To: <20160108065642.GA1215@verge.net.au> First, I'd like to welcome the adoption of the arch/sh/ architecture. On Fri, Jan 8, 2016 at 7:56 AM, Simon Horman <horms@verge.net.au> wrote: > 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. Indeed, following the evolution of the SoC hardware, cfr. below. It meaning has shifted more to the "Linux Renesas mailing list". > 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. Personally, I'd go for option 1. I would even like to propose H8/300 to join, as they share IP cores, too (m32r doesn't, AFAIK). Many old ARM/SH-Mobile SoCs look like SH SoCs with an ARM CPU core bolted on. Recent Renesas ARM SoCs still share many IP cores with older SH SoCs; most of them even have a secondary SH4 CPU core. Using the SH4 CPU core could be useful for doing SH4 work, until J4 becomes mainstream (cfr. old prototype in http://www.spinics.net/lists/linux-sh/msg07188.html). Probably the Jx series won't share IP cores with SH/ARM, but as arch/sh/ maintainers you have to care about older Renesas SH platforms, too. For patchwork, that would mean some more delegation needs to be put in place. So far my 0.05€... Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
next prev parent reply other threads:[~2016-01-08 9:01 UTC|newest] Thread overview: 50+ 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 ` Rich Felker 2016-01-08 4:39 ` [PATCH 1/2] MAINTAINERS: return arch/sh to maintained state, with new maintainers Rich Felker 2016-01-08 4:39 ` Rich Felker 2016-01-11 17:53 ` Peter Zijlstra 2016-01-11 17:53 ` Peter Zijlstra 2016-01-13 1:40 ` Simon Horman 2016-01-13 1:40 ` Simon Horman 2016-01-15 0:52 ` Rich Felker 2016-01-15 0:52 ` Rich Felker 2016-01-15 9:31 ` Geert Uytterhoeven 2016-01-15 9:31 ` Geert Uytterhoeven 2016-01-17 2:32 ` Rich Felker 2016-01-17 2:32 ` Rich Felker 2016-01-17 8:48 ` Geert Uytterhoeven 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 4:40 ` Rich Felker 2016-01-08 6:56 ` Simon Horman 2016-01-08 6:56 ` Simon Horman 2016-01-08 9:01 ` Geert Uytterhoeven [this message] 2016-01-08 9:01 ` Geert Uytterhoeven 2016-01-08 18:21 ` Rich Felker 2016-01-08 18:21 ` Rich Felker 2016-01-08 20:35 ` Geert Uytterhoeven 2016-01-08 20:35 ` Geert Uytterhoeven 2016-01-08 20:52 ` Rich Felker 2016-01-08 20:52 ` Rich Felker 2016-01-10 19:41 ` Geert Uytterhoeven 2016-01-10 19:41 ` Geert Uytterhoeven 2016-01-08 17:35 ` Rob Landley 2016-01-08 17:35 ` Rob Landley 2016-01-08 18:28 ` Laurent Pinchart 2016-01-08 18:28 ` Laurent Pinchart 2016-01-08 19:40 ` Rich Felker 2016-01-08 19:40 ` Rich Felker 2016-01-08 23:15 ` Laurent Pinchart 2016-01-08 23:15 ` Laurent Pinchart 2016-01-08 22:50 ` Rob Landley 2016-01-08 22:50 ` Rob Landley 2016-01-10 20:05 ` Geert Uytterhoeven 2016-01-10 20:05 ` Geert Uytterhoeven 2016-01-11 2:02 ` Rob Landley 2016-01-11 2:02 ` Rob Landley 2016-01-11 2:22 ` uClinux.org 2016-01-11 2:22 ` uClinux.org 2016-01-08 18:51 ` Rich Felker 2016-01-08 18:51 ` Rich Felker 2016-01-08 18:03 ` Sergei Shtylyov 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=CAMuHMdXkK68wM0D2-auNskSDv2ni6R4GabA90We8PbYXikO9Pw@mail.gmail.com \ --to=geert@linux-m68k.org \ --cc=akpm@linux-foundation.org \ --cc=dalias@libc.org \ --cc=horms@verge.net.au \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.