From: Thomas Schwinge <thomas@codesourcery.com>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: <gcc@gcc.gnu.org>, <gcc-patches@gcc.gnu.org>,
Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: [PATCH V6 11/11] bpf: add myself as the maintainer for the eBPF port
Date: Mon, 07 Oct 2019 18:52:00 -0000 [thread overview]
Message-ID: <87h84k1j8u.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <alpine.LSU.2.21.1909081928590.8294@anthias.pfeifer.com>
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
Hi!
On 2019-09-08T19:35:52+0800, Gerald Pfeifer <gerald@pfeifer.com> wrote:
> On Thu, 29 Aug 2019, Jose E. Marchesi wrote:
>> ChangeLog:
>>
>> * MAINTAINERS: Add myself as the maintainer of the eBPF port.
>
> Approved.
>
> As in: Approved by the steering committed assuming the patchset passes
> technical review. :-)
>
> Thanks for working on this, Joe, and congrats to the new hat!
Indeed -- I'm always happy when people/companies demonstrate that good
ol' GCC is still viable for the latest craze, the new shiny thing, like
adding a not-your-standard-CPU-architecture back end! ;-D
I think, using the "as obvious" rule, you should add a "News" item on
<https://gcc.gnu.org/>, like done for other new back ends etc.
Grüße
Thomas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 658 bytes --]
next prev parent reply other threads:[~2019-10-07 18:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 15:32 [PATCH V6 00/11] eBPF support for GCC Jose E. Marchesi
2019-08-29 15:14 ` [PATCH V6 04/11] testsuite: new require effective target indirect_calls Jose E. Marchesi
2019-09-09 9:56 ` Jose E. Marchesi
2019-09-11 18:55 ` Mike Stump
2019-09-11 20:47 ` Jose E. Marchesi
2019-09-12 0:43 ` Mike Stump
2019-08-29 15:14 ` [PATCH V6 03/11] testsuite: annotate c-torture/compile tests with dg-require-stack-size Jose E. Marchesi
2019-09-09 9:52 ` Jose E. Marchesi
2019-09-11 18:42 ` Mike Stump
2019-09-11 20:49 ` Jose E. Marchesi
2019-08-29 15:16 ` [PATCH V6 07/11] bpf: gcc.target eBPF testsuite Jose E. Marchesi
2019-08-29 15:16 ` [PATCH V6 08/11] bpf: make target-supports.exp aware of eBPF Jose E. Marchesi
2019-09-11 18:58 ` Mike Stump
2019-09-12 0:35 ` Mike Stump
2019-08-29 15:18 ` [PATCH V6 11/11] bpf: add myself as the maintainer for the eBPF port Jose E. Marchesi
2019-09-08 11:36 ` Gerald Pfeifer
2019-09-08 16:39 ` Jose E. Marchesi
2019-10-07 18:52 ` Thomas Schwinge [this message]
2019-08-29 15:18 ` [PATCH V6 10/11] bpf: manual updates for eBPF Jose E. Marchesi
2019-08-29 15:20 ` [PATCH V6 01/11] Update config.sub and config.guess Jose E. Marchesi
2019-09-09 9:17 ` Jose E. Marchesi
2019-08-29 15:21 ` [PATCH V6 09/11] bpf: adjust GCC testsuite to eBPF limitations Jose E. Marchesi
2019-09-11 19:04 ` Mike Stump
2019-08-29 15:21 ` [PATCH V6 06/11] bpf: new libgcc port Jose E. Marchesi
2019-08-29 15:34 ` [PATCH V6 02/11] opt-functions.awk: fix comparison of limit, begin and end Jose E. Marchesi
2019-09-09 9:47 ` Jose E. Marchesi
2019-08-29 15:36 ` [PATCH V6 05/11] bpf: new GCC port Jose E. Marchesi
2019-08-30 8:38 ` Richard Sandiford
2019-08-30 10:11 ` Jose E. Marchesi
2019-09-03 18:46 ` Jeff Law
2019-09-05 22:50 ` Jose E. Marchesi
2019-09-11 19:09 ` Mike Stump
2019-09-09 10:23 ` Jose E. Marchesi
2019-10-20 19:51 ` Gerald Pfeifer
2019-10-24 8:45 ` Jose E. Marchesi
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=87h84k1j8u.fsf@euler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jose.marchesi@oracle.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).