From: Vijay Balakrishna <vijayb@linux.microsoft.com>
To: Sascha Hauer <s.hauer@pengutronix.de>, linux-edac@vger.kernel.org
Cc: Borislav Petkov <bp@alien8.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Tony Luck <tony.luck@intel.com>,
James Morse <james.morse@arm.com>,
Robert Richter <rrichter@marvell.com>,
York Sun <york.sun@nxp.com>,
kernel@pengutronix.de, linux-arm-kernel@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Marc Zyngier <maz@kernel.org>
Subject: Re: [PATCH v5 0/2] Add L1 and L2 error detection for A53 and A57
Date: Wed, 12 Mar 2025 18:43:55 -0700 [thread overview]
Message-ID: <ff79f33d-91fd-49e5-9a6f-fa2c32c7021d@linux.microsoft.com> (raw)
In-Reply-To: <20210401110615.15326-1-s.hauer@pengutronix.de>
On 4/1/2021 4:06 AM, Sascha Hauer wrote:
> Hi,
>
> Resending this mainly because Marc Zyngier and Mark Rutland raised
> concerns about using implementation defined registers and I forgot to Cc
> them with the last version. This version, like v4 already, should fix
> these concerns. Looking forward to feedback.
We aim to revive and adapt this patch series for A72 and A78. Is anyone
actively working on this? Please share any information on why it wasn't
pursued and thoughts on adapting it to A72 and A78.
Thanks,
Vijay
next prev parent reply other threads:[~2025-03-13 1:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 11:06 [PATCH v5 0/2] Add L1 and L2 error detection for A53 and A57 Sascha Hauer
2021-04-01 11:06 ` [PATCH 1/2] drivers/edac: " Sascha Hauer
2021-04-02 10:06 ` Marc Zyngier
2021-04-15 10:15 ` Sascha Hauer
2021-04-01 11:06 ` [PATCH 2/2] dt-bindings: arm: cpus: Add edac-enabled property Sascha Hauer
2021-04-01 15:37 ` Marc Zyngier
2025-03-13 1:43 ` Vijay Balakrishna [this message]
2025-03-13 9:22 ` [PATCH v5 0/2] Add L1 and L2 error detection for A53 and A57 Marc Zyngier
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=ff79f33d-91fd-49e5-9a6f-fa2c32c7021d@linux.microsoft.com \
--to=vijayb@linux.microsoft.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-edac@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=rrichter@marvell.com \
--cc=s.hauer@pengutronix.de \
--cc=tony.luck@intel.com \
--cc=york.sun@nxp.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;
as well as URLs for NNTP newsgroup(s).