From: Joel Brobecker <brobecker@adacore.com>
To: Yvan Roux <yvan.roux@foss.st.com>
Cc: "Joel Brobecker" <brobecker@adacore.com>,
"Torbjörn SVENSSON" <torbjorn.svensson@foss.st.com>,
gdb-patches@sourceware.org, tom@tromey.com, pedro@palves.net
Subject: Re: [PATCH v5] gdb/arm: Handle lazy FPU state preservation
Date: Mon, 10 Oct 2022 07:50:22 -0700 [thread overview]
Message-ID: <Y0QxLhfH+7SThi1Q@adacore.com> (raw)
In-Reply-To: <20221010072042.GA9779@gnbcxd0114.gnb.st.com>
> > For the avoidance of doubt, Luis is maintainer for arm and AArch64,
> > so when he says it's good for him, it means the patch is approved
> > for pushing ;-).
>
> Yes thanks for the heads up, I pushed the patch last Friday.
I see; thanks for confirming.
It used to be that we asked people to send a quick reply to the approval
email to confirm that the commit was pushed. In the absence of a review
tool that keeps track of patches, I have found this to be quite useful
to keep track.
> > I don't see you in the list of contributors who have "Write After
> > Approval" privileges. Do all the authors of the patch have an FSF
> > copyright assignment on file? I checked the record, but didn't
> > find anything...
>
> Torbjorn and I are covered by STMicro copyright assignement, so it
> should be fine.
Nice!
--
Joel
next prev parent reply other threads:[~2022-10-10 14:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 8:48 Torbjörn SVENSSON
2022-10-05 14:28 ` Luis Machado
2022-10-09 23:45 ` Joel Brobecker
2022-10-10 7:20 ` Yvan Roux
2022-10-10 9:26 ` Luis Machado
2022-10-10 13:02 ` Pedro Alves
2022-10-10 13:06 ` Luis Machado
2022-10-10 14:50 ` Joel Brobecker [this message]
2022-10-10 16:35 ` Luis Machado
2022-10-10 16:48 ` Joel Brobecker
2022-10-10 16:58 ` Luis Machado
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=Y0QxLhfH+7SThi1Q@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
--cc=tom@tromey.com \
--cc=torbjorn.svensson@foss.st.com \
--cc=yvan.roux@foss.st.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).