From: simon.marchi@polymtl.ca
To: Zied Guermazi <zied.guermazi@trande.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH v4 1/7] configure gdb build system for supporting btrace on arm processors
Date: Sat, 10 Apr 2021 21:45:39 -0400 [thread overview]
Message-ID: <AA76AC13-918F-4C02-A2F0-B05457E9283C@polymtl.ca> (raw)
In-Reply-To: <8547d094-c99a-36ae-25ba-b8180e43c5e5@trande.de>
Ok, can you please make sure to rebase on latest master before sending a patchset? If there are conflicts, it's better to handle them at that moment than later, when the patch is approved.
You could also look into the --base option of format-patch to record the base commit in the generated patches.
Simon
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2021-04-11 1:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 21:17 [PATCH v4 0/7] extend branch tracing to use ARM CoreSight traces Zied Guermazi
2021-04-10 21:17 ` [PATCH v4 1/7] configure gdb build system for supporting btrace on arm processors Zied Guermazi
2021-04-10 22:40 ` Simon Marchi
2021-04-11 0:35 ` Zied Guermazi
2021-04-11 1:09 ` Simon Marchi
2021-04-11 1:14 ` Zied Guermazi
2021-04-11 1:45 ` simon.marchi [this message]
2021-04-10 21:17 ` [PATCH v4 2/7] add btrace coresight related commands Zied Guermazi
2021-04-11 6:41 ` Eli Zaretskii
2021-04-10 21:17 ` [PATCH v4 3/7] start/stop btrace with coresight etm and parse etm buffer. nat independant Zied Guermazi
2021-04-10 21:17 ` [PATCH v4 4/7] start/stop btrace with coresight etm and collect etm buffer on linux os Zied Guermazi
2021-04-10 21:17 ` [PATCH v4 5/7] fix issue: gdb hangs in the command following a commad returning with TARGET_WAITKIND_NO_HISTORY Zied Guermazi
2021-04-10 21:17 ` [PATCH v4 6/7] add support for coresight btrace via remote protocol Zied Guermazi
2021-04-11 6:43 ` Eli Zaretskii
2021-04-10 21:17 ` [PATCH v4 7/7] adapt btrace testcases for arm target Zied Guermazi
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=AA76AC13-918F-4C02-A2F0-B05457E9283C@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=zied.guermazi@trande.de \
/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).