Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis <luis.machado.foss@gmail.com>
To: Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
	Srinath Parvathaneni <Srinath.Parvathaneni@arm.com>
Cc: GDB Patches <gdb-patches@sourceware.org>,
	"guinevere@redhat.com" <guinevere@redhat.com>,
	Ezra Sitorus <Ezra.Sitorus@arm.com>,
	Matthieu Longo <Matthieu.Longo@arm.com>,
	"simark@simark.ca" <simark@simark.ca>,
	Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH v3 1/5] [PATCH 1/5] gdb/aarch64: Add POR_EL0 register support for FEAT_S1POE
Date: Wed, 12 Aug 2026 22:33:08 +0100	[thread overview]
Message-ID: <1a136e9c-b9cc-47e6-b4d0-1eb8271ce810@gmail.com> (raw)
In-Reply-To: <878q6c8cmo.fsf@linaro.org>

On 12/08/2026 00:23, Thiago Jung Bauermann wrote:
> Hello,
> 
> Srinath Parvathaneni <Srinath.Parvathaneni@arm.com> writes:
> 
>> Hi Luis/Thiago,
>>
>> After looking at the suggestions in the thread, I made a few changes to the
>> POR_EL0 interface. The custom display for por_el0 has been updated, and I've
>> also added support for pseudo registers for the individual permission fields.
>>
>> Could you please have a look at the output below? If this looks ok, I'll re-spin
>> the series, address the remaining review comments and send it out for another
>> review.
> 
> I like this output. I'd like to see what Luis thinks but IMHO it's a
> nice improvement over the previous versions, and is a usable way of
> working with the POR and its individual permissions.
>
Agreed. I like the new format better.

  reply	other threads:[~2026-08-12 21:33 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 20:15 [PATCH v3 0/5] " srinath.parvathaneni
2026-07-14 20:15 ` [PATCH v3 1/5] [PATCH 1/5] " srinath.parvathaneni
2026-07-21 19:53   ` Luis
2026-07-25  6:20     ` Thiago Jung Bauermann
2026-07-25  7:37       ` Luis
2026-07-25 18:44         ` Thiago Jung Bauermann
2026-08-07 19:51           ` Srinath Parvathaneni
2026-08-11 23:23             ` Thiago Jung Bauermann
2026-08-12 21:33               ` Luis [this message]
2026-08-12 21:32             ` Luis
2026-07-21 20:25   ` Luis
2026-07-23  9:29     ` Srinath Parvathaneni
2026-07-25  6:13       ` Thiago Jung Bauermann
2026-07-25  7:29         ` Luis
2026-07-14 20:15 ` [PATCH v3 2/5] [PATCH 2/5] gdb: Improve SIGSEGV diagnostics for POE faults srinath.parvathaneni
2026-07-21 20:30   ` Luis
2026-07-22  9:41     ` Matthieu Longo
2026-07-22 23:11       ` Luis
2026-07-23  9:03         ` Srinath Parvathaneni
2026-07-25  7:39           ` Luis
2026-07-14 20:15 ` [PATCH v3 3/5] [PATCH 3/5] gdbserver/aarch64: Add POR_EL0 register support srinath.parvathaneni
2026-07-14 20:15 ` [PATCH v3 4/5] [PATCH 4/5] gdb/aarch64: Add core file support for FEAT_S1POE srinath.parvathaneni
2026-07-21 20:14   ` Luis
2026-07-14 20:15 ` [PATCH v3 5/5] [PATCH 5/5] gdb/testsuite: Add FEAT_S1POE testcases srinath.parvathaneni
2026-07-21 20:38   ` Luis
2026-07-25  6:23   ` Thiago Jung Bauermann

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=1a136e9c-b9cc-47e6-b4d0-1eb8271ce810@gmail.com \
    --to=luis.machado.foss@gmail.com \
    --cc=Ezra.Sitorus@arm.com \
    --cc=Matthieu.Longo@arm.com \
    --cc=Srinath.Parvathaneni@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=guinevere@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=simark@simark.ca \
    --cc=thiago.bauermann@linaro.org \
    /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