From: Luis Machado <luis.machado@arm.com>
To: Carl Love <cel@linux.ibm.com>,
Guinevere Larsen <blarsen@redhat.com>,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
gdb-patches@sourceware.org
Cc: Pedro Alves <pedro@palves.net>, Tom Tromey <tom@tromey.com>,
Simon Marchi <simark@simark.ca>
Subject: Re: [ PATCH 0/3] Fix GDB reverse execution behavior
Date: Mon, 11 Dec 2023 14:40:51 +0000 [thread overview]
Message-ID: <41d5c5dd-3e34-417b-a613-f3ca1a27112a@arm.com> (raw)
In-Reply-To: <bd5ee47f-1bcf-4e04-a6a8-efe4f75cabe5@arm.com>
Hi Carl,
On 11/30/23 15:43, Luis Machado wrote:
> On 11/30/23 15:39, Carl Love wrote:
>> Guinevere:
>>
>> On Thu, 2023-11-30 at 12:36 +0100, Guinevere Larsen wrote:
>>> On a side note, b4 didn't really like this series and I'm not sure
>>> why.
>>> My guess is that all 3 patches have the same email subject, but it
>>> may
>>> also be that I needed --3way when using git am. Either way, just
>>> mentioning to gather knowledge on what b4 likes or doesn't like.
>>
>>
>> I am not familiar with b4. I just did a Google search and found a
>> description of it at:
>>
>> https://people.kernel.org/monsieuricon/introducing-b4-and-patch-attestation
>>
>> It seems to be a tool the maintainers can use for patch management. I
>> will have to play around with it and see if I can figure out why b4
>> doesn't like the patch series.
>>
>> Is this something that people have started using?
>
> I started to use it more recently. It makes it pretty easy to download a
> series and apply to a tree.
>
> For instance, take this entry: https://inbox.sourceware.org/gdb-patches/85a2f33d4ad12966dcb212e99e836175b69fddee.camel@linux.ibm.com/T/#t
>
> You could do this to fetch the patches:
>
>
> b4 am -M https://inbox.sourceware.org/gdb-patches/85a2f33d4ad12966dcb212e99e836175b69fddee.camel@linux.ibm.com/T/#t -o /tmp/
> Looking up https://inbox.sourceware.org/gdb-patches/85a2f33d4ad12966dcb212e99e836175b69fddee.camel@linux.ibm.com
> Grabbing thread from inbox.sourceware.org/gdb-patches/85a2f33d4ad12966dcb212e99e836175b69fddee.camel@linux.ibm.com/t.mbox.gz
> Analyzing 12 messages in the thread
> Checking attestation on all messages, may take a moment...
> ---
> ✓ [PATCH 1/3] Fix GDB reverse execution behavior
> + Tested-By: Luis Machado <luis.machado@arm.com> (✓ DKIM/armh.onmicrosoft.com)
> + Reviewed-By: Luis Machado <luis.machado@arm.com> (✓ DKIM/armh.onmicrosoft.com)
> ✓ [PATCH 2/3] Fix GDB reverse execution behavior
> + Tested-By: Luis Machado <luis.machado@arm.com> (✓ DKIM/armh.onmicrosoft.com)
> + Reviewed-By: Luis Machado <luis.machado@arm.com> (✓ DKIM/armh.onmicrosoft.com)
> ✓ [PATCH 3/3] Fix GDB reverse execution behavior
> + Tested-By: Luis Machado <luis.machado@arm.com> (✓ DKIM/armh.onmicrosoft.com)
> + Reviewed-By: Luis Machado <luis.machado@arm.com> (✓ DKIM/armh.onmicrosoft.com)
> ---
> ✓ Signed: DKIM/ibm.com (From: cel@linux.ibm.com)
> ---
> Total patches: 3
> ---
> NOTE: Some trailers were sent to the cover letter:
> Reviewed-By: Guinevere Larsen <blarsen@redhat.com>
> NOTE: Rerun with -t to apply them to all patches
> ---
> Cover: /tmp/20231122_cel_fix_gdb_reverse_execution_behavior.cover
> Link: https://lore.kernel.org/r/5483d77c72088a1e4d5dfed2eded2366643fc659.camel@linux.ibm.com
> Base: not specified
> git am /tmp/20231122_cel_fix_gdb_reverse_execution_behavior.maildir
>
> And then you can easily apply the series with the above git am command.
Let's wait until this Friday to see if there is any other feedback regarding this series.
Otherwise, LGTM.
Approved-By: Luis Machado <luis.machado@arm.com>
next prev parent reply other threads:[~2023-12-11 14:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f624c5566d6a8a1014ecc38900ca1ba0202989ef.camel@linux.ibm.com>
[not found] ` <890101c23dd5fa60fcbf9d4b299cb2a533c260b7.camel@linux.ibm.com>
[not found] ` <1e702d8f-e5b4-4719-b1e7-42210f350305@arm.com>
[not found] ` <a01f4e5f3fd399e3a9a971421265b34d08e32388.camel@linux.ibm.com>
[not found] ` <643afce1-ab9b-4e8b-bcbb-5738dc409a28@arm.com>
[not found] ` <9e17008084c34f953f5318933436ec703250120a.camel@linux.ibm.com>
[not found] ` <92a751d1-a4b9-4c21-821e-a1dc67207516@arm.com>
[not found] ` <ee4ed81911a3196327c2aea3fa9a77f910a5e798.camel@linux.ibm.com>
2023-11-22 23:33 ` Carl Love
2023-11-30 11:36 ` Guinevere Larsen
2023-11-30 15:39 ` Carl Love
2023-11-30 15:43 ` Luis Machado
2023-12-11 14:40 ` Luis Machado [this message]
2023-12-14 16:10 ` Carl Love
2024-01-02 22:52 ` Carl Love
2023-11-30 15:45 ` Guinevere Larsen
2023-11-22 23:33 ` [ PATCH 1/3] " Carl Love
2023-11-29 11:44 ` Luis Machado
2023-11-29 16:30 ` Carl Love
2023-11-29 16:38 ` Luis Machado
2023-11-22 23:33 ` [ PATCH 2/3] " Carl Love
2023-11-29 11:44 ` Luis Machado
2023-11-22 23:33 ` [PATCH 3/3] " Carl Love
2023-11-29 11:46 ` Luis Machado
2023-11-29 16:30 ` Carl Love
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=41d5c5dd-3e34-417b-a613-f3ca1a27112a@arm.com \
--to=luis.machado@arm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=blarsen@redhat.com \
--cc=cel@linux.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
--cc=simark@simark.ca \
--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