From: Thomas Schwinge <thomas@codesourcery.com>
To: Ulrich Weigand <uweigand@de.ibm.com>, <gcc-patches@gcc.gnu.org>
Cc: <dje.gcc@gmail.com>
Subject: Re: [RFA][1/3] Remove Cell Broadband Engine SPU targets
Date: Tue, 08 Oct 2019 10:32:00 -0000 [thread overview]
Message-ID: <875zkz1qbd.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <20190902201653.10222D802F0@oc3748833570.ibm.com>
[-- Attachment #1.1: Type: text/plain, Size: 995 bytes --]
Hi!
On 2019-09-02T22:16:52+0200, "Ulrich Weigand" <uweigand@de.ibm.com> wrote:
> * MAINTAINERS: Remove spu port maintainers.
> --- MAINTAINERS (revision 275321)
> +++ MAINTAINERS (working copy)
> @@ -109,9 +109,6 @@
> sh port Oleg Endo <olegendo@gcc.gnu.org>
> sparc port David S. Miller <davem@redhat.com>
> sparc port Eric Botcazou <ebotcazou@libertysurf.fr>
> -spu port Trevor Smigiel <trevor_smigiel@playstation.sony.com>
> -spu port David Edelsohn <dje.gcc@gmail.com>
> -spu port Ulrich Weigand <uweigand@de.ibm.com>
> tilegx port Walter Lee <walt@tilera.com>
> tilepro port Walter Lee <walt@tilera.com>
> v850 port Nick Clifton <nickc@redhat.com>
In r276692, I committed the attached to "Add back Trevor Smigiel; move
into Write After Approval section", assuming that it was just an
oversight that he got dropped from the file, as he -- in contrast to
David and Ulrich -- doesn't remain listed with other roles.
Grüße
Thomas
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 0001-Remove-Cell-Broadband-Engine-SPU-targets.trunk.patch --]
[-- Type: text/x-diff, Size: 1438 bytes --]
From 1be3a79f2a6fbc0cb095474a3ab8f96398efa24c Mon Sep 17 00:00:00 2001
From: tschwinge <tschwinge@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Tue, 8 Oct 2019 10:20:50 +0000
Subject: [PATCH 3/3] Remove Cell Broadband Engine SPU targets
Follow-up to trunk 275343:
* MAINTAINERS: Add back Trevor Smigiel; move into Write After
Approval section.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@276692 138bc75d-0d04-0410-961f-82ee72b054a4
---
ChangeLog | 5 +++++
MAINTAINERS | 1 +
2 files changed, 6 insertions(+)
diff --git a/ChangeLog b/ChangeLog
index fb901e4a39e..90413f57284 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2019-10-08 Thomas Schwinge <thomas@codesourcery.com>
+
+ * MAINTAINERS: Add back Trevor Smigiel; move into Write After
+ Approval section.
+
2019-10-01 Frederik Harwath <frederik@codesourcery.com>
* MAINTAINERS: Add myself to Write After Approval
diff --git a/MAINTAINERS b/MAINTAINERS
index bd6a7d44c5a..78f17c35e9e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -585,6 +585,7 @@ Sharad Singhai <singhai@google.com>
Johannes Singler <singler@kit.edu>
Franz Sirl <franz.sirl-kernel@lauterbach.com>
Jan Sjodin <jan.sjodin@amd.com>
+Trevor Smigiel <trevor_smigiel@playstation.sony.com>
Edward Smith-Rowland <3dw4rd@verizon.net>
Jayant Sonar <rsonar.jayant@gmail.com>
Anatoly Sokolov <aesok@post.ru>
--
2.17.1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 658 bytes --]
next prev parent reply other threads:[~2019-10-08 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 20:17 Ulrich Weigand
2019-09-03 14:16 ` Jeff Law
2019-10-28 9:38 ` Eric Botcazou
2019-10-08 10:32 ` Thomas Schwinge [this message]
2019-10-08 16:29 ` Ulrich Weigand
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=875zkz1qbd.fsf@euler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=uweigand@de.ibm.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).