Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com
Subject: Re: [PATCH 0/4] arm64/sysreg: Add registers for FEAT_Debugv8p9
Date: Tue, 30 Apr 2024 18:08:51 +0530	[thread overview]
Message-ID: <34790012-fd1b-4e35-8e18-16ed2d060b65@arm.com> (raw)
In-Reply-To: <20240430122738.GB13690@willie-the-truck>



On 4/30/24 17:57, Will Deacon wrote:
> On Mon, Apr 29, 2024 at 07:26:34AM +0530, Anshuman Khandual wrote:
>> On 4/17/24 07:47, Anshuman Khandual wrote:
>>> This series adds relevant registers and their fields which are required for
>>> enabling FEAT_Debugv8p9. These patches have been split out from the earlier
>>> series discussed below. This series applies on v6.9-rc4
>>>
>>> https://lore.kernel.org/all/20240405080008.1225223-1-anshuman.khandual@arm.com/
>>>
>>> Changes from RFC:
>>>
>>> - Updated the document number from DDI0601 2023-12 to 2024-03
>>>
>>> Anshuman Khandual (4):
>>>   arm64/sysreg: Add register fields for MDSELR_EL1
>>>   arm64/sysreg: Add register fields for HDFGRTR2_EL2
>>>   arm64/sysreg: Add register fields for HDFGWTR2_EL2
>>>   arm64/sysreg: Update ID_AA64MMFR0_EL1 register
>>>
>>>  arch/arm64/tools/sysreg | 68 +++++++++++++++++++++++++++++++++++++++++
>>>  1 file changed, 68 insertions(+)
>>>
>>
>> Gentle ping, any updates on this series ?
> 
> Not sure why you dropped me from cc but, as with your other change [1],

Ahh that was my bad ! All individual patches here have your email marked in
their CC but then forgot to add the combined email set (what I normally do),
in the cover letter itself, making original --cc-cover pointless. This email
was in response to the cover-letter email thread, thus repeating the same
problem all over again. Apologies for the same.

> I don't see the point in taking these on their own. Just keep them with
> your hw_breakpoint series [2] when you post a new version taking into
> account the feedback from Marc.

Sure, will do that.

> 
> Will
> 
> [1] https://lore.kernel.org/all/20240419021325.2880384-1-anshuman.khandual@arm.com/
> [2] https://lore.kernel.org/all/20240405080008.1225223-1-anshuman.khandual@arm.com/

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2024-04-30 12:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17  2:17 [PATCH 0/4] arm64/sysreg: Add registers for FEAT_Debugv8p9 Anshuman Khandual
2024-04-17  2:17 ` [PATCH 1/4] arm64/sysreg: Add register fields for MDSELR_EL1 Anshuman Khandual
2024-04-17  2:17 ` [PATCH 2/4] arm64/sysreg: Add register fields for HDFGRTR2_EL2 Anshuman Khandual
2024-04-17  2:17 ` [PATCH 3/4] arm64/sysreg: Add register fields for HDFGWTR2_EL2 Anshuman Khandual
2024-04-17  2:17 ` [PATCH 4/4] arm64/sysreg: Update ID_AA64MMFR0_EL1 register Anshuman Khandual
2024-04-29  1:56 ` [PATCH 0/4] arm64/sysreg: Add registers for FEAT_Debugv8p9 Anshuman Khandual
2024-04-30 12:27   ` Will Deacon
2024-04-30 12:38     ` Anshuman Khandual [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=34790012-fd1b-4e35-8e18-16ed2d060b65@arm.com \
    --to=anshuman.khandual@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=will@kernel.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