From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Paul Mundt <paul.mundt@gmail.com>,
Magnus Damm <magnus.damm@gmail.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Andrew Morton <akpm@linux-foundation.org>,
Paul Bolle <pebolle@tiscali.nl>,
Linux-sh list <linux-sh@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@linux-m68k.org>
Subject: Re: [PATCH v2] MAINTAINERS: Mark SuperH orphan
Date: Mon, 17 Feb 2014 21:28:55 +0900 [thread overview]
Message-ID: <20140217122854.GD23509@verge.net.au> (raw)
In-Reply-To: <CAMuHMdXG+L1umNA1eBMizJnvw599Z-qbcSpSt8PsNyk1YESBjA@mail.gmail.com>
On Mon, Feb 17, 2014 at 01:14:53PM +0100, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Mon, Feb 17, 2014 at 12:55 PM, Simon Horman <horms@verge.net.au> wrote:
> > The change includes the maintenance of drivers/sh/ and I believe that
> > the CPG driver in drivers/sh/clk, the INTC driver in drivers/sh/intc and
> > the code in pm_runtime.c is used by Renesas ARM based SoCs.
> > It seems somewhat unsatisfactory to orphan that code.
>
> Indeed, everything but drivers/sh/intc/balancing.c, drivers/sh/maple/
> and drivers/sh/superhyway/ is also used on ARM/SHMOBILE.
> But that's in-se unrelated to marking the SuperH architecture as orphaned.
>
> > What I propose is adding entries for them, either stand-alone or part of
> > the SHMOBILE (a.k.a. Renesas ARM based SoCs) entry so that are maintained
> > by someone. I am happy for my name to go against that.
>
> Apparently the "ARM/SHMOBILE ARM ARCHITECTURE" entry already
> has drivers/sh/ listed, so you (and Magnus) are already in charge.
Wonderful, that addresses my concern quite nicely.
prev parent reply other threads:[~2014-02-17 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 21:36 Geert Uytterhoeven
2014-02-17 11:55 ` Simon Horman
2014-02-17 12:14 ` Geert Uytterhoeven
2014-02-17 12:28 ` Simon Horman [this message]
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=20140217122854.GD23509@verge.net.au \
--to=horms@verge.net.au \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=akpm@linux-foundation.org \
--cc=geert+renesas@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=paul.mundt@gmail.com \
--cc=pebolle@tiscali.nl \
/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
all inboxes | Powered by JetHome®