From: Patrick O'Neill <patrick@rivosinc.com>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: gcc-patches@gcc.gnu.org, gnu-toolchain@rivosinc.com,
jeffreyalaw@gmail.com
Subject: [committed] MAINTAINERS: Add myself to write after approval
Date: Wed, 26 Apr 2023 09:15:29 -0700 [thread overview]
Message-ID: <7fc0fe6c-a663-d71f-271d-85a726d808a7@rivosinc.com> (raw)
In-Reply-To: <mhng-30d0ad65-441e-40fc-a5bc-bc3604b22369@palmer-ri-x1c9>
On 4/26/23 09:08, Palmer Dabbelt wrote:
> On Wed, 26 Apr 2023 09:07:05 PDT (-0700), Patrick O'Neill wrote:
>> 2023-04-26 Patrick O'Neill <patrick@rivosinc.com>
>>
>> * MAINTAINERS: Add myself.
>>
>> Signed-off-by: Patrick O'Neill <patrick@rivosinc.com>
>> ---
>> MAINTAINERS | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index d2188c3275a..169418d44f7 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -578,6 +578,7 @@ Dorit Nuzman <dorit@il.ibm.com>
>> David O'Brien <obrien@FreeBSD.org>
>> Carlos O'Donell <carlos@redhat.com>
>> Peter O'Gorman <pogma@thewrittenword.com>
>> +Patrick O'Neill <patrick@rivosinc.com>
>> Braden Obrzut <admin@maniacsvault.net>
>> Andrea Ornstein <andrea.ornstein@st.com>
>> Maxim Ostapenko <m.ostapenko@samsung.com>
>
> Acked-by: Palmer Dabbelt <palmer@rivosinc.com>
>
> Thanks!
Committed!
Patrick
next prev parent reply other threads:[~2023-04-26 16:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 16:07 [PATCH] " Patrick O'Neill
2023-04-26 16:08 ` Palmer Dabbelt
2023-04-26 16:15 ` Patrick O'Neill [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-09 21:14 [COMMITTED] " Jivan Hakobyan
2023-10-10 12:40 Christoph Muellner
2023-08-29 11:23 Tsukasa OI
2023-08-11 17:30 Eric Feng
2023-08-01 13:56 [committed] " Richard Ball
2023-07-31 1:25 Li Xu
2023-07-21 18:11 [COMMITTED] " Cupertino Miranda
2023-06-25 9:51 [committed] " Lehua Ding
2023-05-10 16:10 pan2.li
2022-09-23 10:39 [committed] MAINTAINERS: Add myself to Write After Approval Paul-Antoine Arras
2022-07-15 13:50 Andrew Carlotti
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=7fc0fe6c-a663-d71f-271d-85a726d808a7@rivosinc.com \
--to=patrick@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu-toolchain@rivosinc.com \
--cc=jeffreyalaw@gmail.com \
--cc=palmer@rivosinc.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).