All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms+renesas@verge.net.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	linux-renesas-soc@vger.kernel.org, linux-sh@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Simon Horman <horms+renesas@verge.net.au>
Subject: [PATCH] MAINTAINERS: Update mailing list for Renesas ARM64 SoC Development
Date: Thu, 21 Jan 2016 06:21:16 +0000	[thread overview]
Message-ID: <1453357276-10148-1-git-send-email-horms+renesas@verge.net.au> (raw)
In-Reply-To: <1453079073-30937-1-git-send-email-horms+renesas@verge.net.au>

Update the mailing list used for development of support for
ARM64 Renesas SoCs.

This is a follow-up for a similar change for other Renesas SoCs and
drivers uses by Renesas SoCs. The ARM64 SoC entry was not updated in
that patch as it was not yet present in mainline.

The motivation for the mailing list update is that 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: Magnus Damm <magnus.damm@gmail.com>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
 MAINTAINERS | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 293874ca4d4e..0331ce2a6dc6 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1439,8 +1439,8 @@ S:	Maintained
 ARM/RENESAS ARM64 ARCHITECTURE
 M:	Simon Horman <horms@verge.net.au>
 M:	Magnus Damm <magnus.damm@gmail.com>
-L:	linux-sh@vger.kernel.org
-Q:	http://patchwork.kernel.org/project/linux-sh/list/
+L:	linux-renesas-soc@vger.kernel.org
+Q:	http://patchwork.kernel.org/project/linux-renesas-soc/list/
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git next
 S:	Supported
 F:	arch/arm64/boot/dts/renesas/
-- 
2.1.4


WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms+renesas@verge.net.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	linux-renesas-soc@vger.kernel.org, linux-sh@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Simon Horman <horms+renesas@verge.net.au>
Subject: [PATCH] MAINTAINERS: Update mailing list for Renesas ARM64 SoC Development
Date: Thu, 21 Jan 2016 15:21:16 +0900	[thread overview]
Message-ID: <1453357276-10148-1-git-send-email-horms+renesas@verge.net.au> (raw)

Update the mailing list used for development of support for
ARM64 Renesas SoCs.

This is a follow-up for a similar change for other Renesas SoCs and
drivers uses by Renesas SoCs. The ARM64 SoC entry was not updated in
that patch as it was not yet present in mainline.

The motivation for the mailing list update is that 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: Magnus Damm <magnus.damm@gmail.com>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
 MAINTAINERS | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 293874ca4d4e..0331ce2a6dc6 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1439,8 +1439,8 @@ S:	Maintained
 ARM/RENESAS ARM64 ARCHITECTURE
 M:	Simon Horman <horms@verge.net.au>
 M:	Magnus Damm <magnus.damm@gmail.com>
-L:	linux-sh@vger.kernel.org
-Q:	http://patchwork.kernel.org/project/linux-sh/list/
+L:	linux-renesas-soc@vger.kernel.org
+Q:	http://patchwork.kernel.org/project/linux-renesas-soc/list/
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git next
 S:	Supported
 F:	arch/arm64/boot/dts/renesas/
-- 
2.1.4

  parent reply	other threads:[~2016-01-21  6:21 UTC|newest]

Thread overview: 34+ 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:04 ` Simon Horman
2016-01-18  1:53 ` Khiem Nguyen
2016-01-18  1:53   ` Khiem Nguyen
2016-01-18  1:53   ` Khiem Nguyen
2016-01-18  2:27   ` Yoshihiro Shimoda
2016-01-18  2:27     ` Yoshihiro Shimoda
2016-01-18  4:48     ` Simon Horman
2016-01-18  4:48       ` Simon Horman
2016-01-18  4:48       ` Simon Horman
2016-01-18  5:09 ` Magnus Damm
2016-01-18  5:09   ` Magnus Damm
2016-01-18  8:09 ` Geert Uytterhoeven
2016-01-18  8:09   ` Geert Uytterhoeven
2016-01-18  8:09   ` Geert Uytterhoeven
2016-01-18  8:09   ` Geert Uytterhoeven
2016-01-19  0:18   ` Simon Horman
2016-01-19  0:18     ` Simon Horman
2016-01-19  0:18     ` Simon Horman
2016-01-19  0:18     ` Simon Horman
2016-01-18 11:58 ` Wolfram Sang
2016-01-18 11:58   ` Wolfram Sang
2016-01-18 22:44 ` Laurent Pinchart
2016-01-18 22:44   ` Laurent Pinchart
2016-01-19  5:01 ` Rich Felker
2016-01-19  5:01   ` Rich Felker
2016-01-19 11:10 ` Sergei Shtylyov
2016-01-19 11:10   ` Sergei Shtylyov
2016-01-21  6:21 ` Simon Horman [this message]
2016-01-21  6:21   ` [PATCH] MAINTAINERS: Update mailing list for Renesas ARM64 " Simon Horman
2016-01-21  7:29   ` Magnus Damm
2016-01-21  7:29     ` Magnus Damm
2016-01-21  8:25   ` Geert Uytterhoeven
2016-01-21  8:25     ` Geert Uytterhoeven

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=1453357276-10148-1-git-send-email-horms+renesas@verge.net.au \
    --to=horms+renesas@verge.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.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 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.