From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-renesas-soc@vger.kernel.org,
Linux-sh list <linux-sh@vger.kernel.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
linux-pci <linux-pci@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH] MAINTAINERS: Update mailing list for Renesas SoC Development
Date: Tue, 19 Jan 2016 09:18:16 +0900 [thread overview]
Message-ID: <20160119001815.GA14224@verge.net.au> (raw)
In-Reply-To: <CAMuHMdXF8QnKsLOYFnT7Rje5G9_7Xr0NesO2SKEkWSivKQYkbA@mail.gmail.com>
On Mon, Jan 18, 2016 at 09:09:29AM +0100, Geert Uytterhoeven wrote:
> CC linux-arm-kernel
>
> On Mon, Jan 18, 2016 at 2:04 AM, Simon Horman
> <horms+renesas@verge.net.au> wrote:
> > Update the mailing list used for development of support for
> > Renesas SoCs and related drivers.
> >
> > Up until now the linux-sh mailing list has been used, however,
> > Renesas SoCs are now much wider than the SH architecture and there
> > is some desire from some for the linux-sh list to refocus on
> > discussion of the work on the SH architecture.
> >
> > Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> > Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > Cc: Geert Uytterhoeven <geert+renesas@glider.be>
> > Cc: Magnus Damm <magnus.damm@gmail.com>
> > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
>
> Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> > ---
> > * This patch applies on top of Linus's tree where currently the head commit
> > is 984065055e6e ("Merge branch 'drm-next' of
> > git://people.freedesktop.org/~airlied/linux")
> >
> > This has been used as a base instead of v4.4 so that it is based on the
> > following two commits which affect it:
> > - 1a4ca6dd3dc8 ("MAINTAINERS: Add co-maintainer for Renesas Pin Controllers")
> > - 3e46c3973cba ("MAINTAINERS: add Renesas usb2 phy driver")
>
> I assume you'll send an update for the "ARM/RENESAS ARM64 ARCHITECTURE"
> section as soon as that has landed in mainline?
Yes, that is my plan.
next prev parent reply other threads:[~2016-01-19 0:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 1:04 [PATCH] MAINTAINERS: Update mailing list for Renesas SoC Development Simon Horman
2016-01-18 1:53 ` Khiem Nguyen
2016-01-18 2:27 ` Yoshihiro Shimoda
2016-01-18 4:48 ` Simon Horman
2016-01-18 5:09 ` Magnus Damm
2016-01-18 8:09 ` Geert Uytterhoeven
2016-01-19 0:18 ` Simon Horman [this message]
2016-01-18 11:58 ` Wolfram Sang
2016-01-18 22:44 ` Laurent Pinchart
2016-01-19 5:01 ` Rich Felker
2016-01-19 11:10 ` 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=20160119001815.GA14224@verge.net.au \
--to=horms@verge.net.au \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=torvalds@linux-foundation.org \
/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).