From: "Yan, Zhiyong" <Zhiyong.Yan@windriver.com>
To: Tom Tromey <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: The patch for bugzilla 30387
Date: Thu, 11 May 2023 06:26:48 +0000 [thread overview]
Message-ID: <DS0SPRMB00013F2DD7A100D051B8ED61E7749@DS0SPRMB0001.namprd11.prod.outlook.com> (raw)
In-Reply-To: <87cz385gkp.fsf@tromey.com>
Hi Tom,
Thank you for your feedback.
I followed https://sourceware.org/gdb/wiki/ContributionChecklist, using git send-email, to send patch review quest to gdb-batches@sourceware.org.
Best Regards.
Zhiyong
-----Original Message-----
From: Tom Tromey <tom@tromey.com>
Sent: Wednesday, May 10, 2023 11:53 PM
To: Yan, Zhiyong <Zhiyong.Yan@windriver.com>
Cc: gdb-patches@sourceware.org
Subject: Re: The patch for bugzilla 30387
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know the content is safe.
>>>>> Yan, Zhiyong <Zhiyong.Yan@windriver.com> writes:
> How is this patch going ?
...
> There is a patch for https://sourceware.org/bugzilla/show_bug.cgi?id=30387, in the attachment.
> Bugzilla 30387 has given the steps of producing this issue on arm platform.
Normally the gdb project doesn't do patch review in bugzilla.
The best thing to do is follow the contribution instructions, and send
the patch to this list.
The instructions are here:
https://sourceware.org/gdb/wiki/ContributionChecklist
thanks,
Tom
prev parent reply other threads:[~2023-05-11 6:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 2:13 Yan, Zhiyong
2023-05-08 1:24 ` Yan, Zhiyong
2023-05-10 15:52 ` Tom Tromey
2023-05-11 6:26 ` Yan, Zhiyong [this message]
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=DS0SPRMB00013F2DD7A100D051B8ED61E7749@DS0SPRMB0001.namprd11.prod.outlook.com \
--to=zhiyong.yan@windriver.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).