public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Zied Guermazi <zied.guermazi@trande.de>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH v4 1/7] configure gdb build system for supporting btrace on arm processors
Date: Sun, 11 Apr 2021 03:14:01 +0200	[thread overview]
Message-ID: <8547d094-c99a-36ae-25ba-b8180e43c5e5@trande.de> (raw)
In-Reply-To: <1326f44a-a0b6-5f35-ee32-9cc2fc9c6a79@polymtl.ca>

hi Simon

I am still using the commit "39b07596938e4c2a7251d77ea01981d475747599" 
as base

/Zied

On 11.04.21 03:09, Simon Marchi wrote:
> On 2021-04-10 8:35 p.m., Zied Guermazi wrote:
>> hi Simon
>>
>> this patch set was generated using the command "git format-patch --cover-letter  -7".
>>
>> the patch set was edited manually to add the mail body up to the three dashes "---".
> Typically I would just write the "mail body" as the git commit message,
> not by editing the .patch files.  But that should still be ok.
>
>> it was then send using the command "git send-email *.patch".
> That all looks good, that's why it's puzzling.  What's your base commit
> for v4?
>
> Simon
-- 

*Zied Guermazi*
founder

Trande UG
Leuschnerstraße 2
69469 Weinheim/Germany

Mobile: +491722645127
mailto:zied.guermazi@trande.de

*Trande UG*
Leuschnerstraße 2, D-69469 Weinheim; Telefon: +491722645127
Sitz der Gesellschaft: Weinheim- Registergericht: AG Mannheim HRB 736209 
- Geschäftsführung: Zied Guermazi

*Confidentiality Note*
This message is intended only for the use of the named recipient(s) and 
may contain confidential and/or privileged information. If you are not 
the intended recipient, please contact the sender and delete the 
message. Any unauthorized use of the information contained in this 
message is prohibited.



  reply	other threads:[~2021-04-11  1:14 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 [this message]
2021-04-11  1:45           ` simon.marchi
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=8547d094-c99a-36ae-25ba-b8180e43c5e5@trande.de \
    --to=zied.guermazi@trande.de \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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).