From: Conor Dooley <mail@conchuod.ie>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
linux-riscv@lists.infradead.org, stable@vger.kernel.org,
Palmer Dabbelt <palmer@dabbelt.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Albert Ou <aou@eecs.berkeley.edu>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Walmsley <paul.walmsley@sifive.com>,
Atish Patra <atishp@atishpatra.org>,
Emil Renner Berthing <emil.renner.berthing@canonical.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH 1/1] riscv: dts: microchip: correct L2 cache interrupts
Date: Thu, 18 Aug 2022 21:19:49 +0100 [thread overview]
Message-ID: <166085385179.1336923.6007777550886077496.b4-ty@microchip.com> (raw)
In-Reply-To: <20220817132521.3159388-1-heinrich.schuchardt@canonical.com>
From: Conor Dooley <conor.dooley@microchip.com>
On Wed, 17 Aug 2022 15:25:21 +0200, Heinrich Schuchardt wrote:
> The "PolarFire SoC MSS Technical Reference Manual" documents the
> following PLIC interrupts:
>
> 1 - L2 Cache Controller Signals when a metadata correction event occurs
> 2 - L2 Cache Controller Signals when an uncorrectable metadata event occurs
> 3 - L2 Cache Controller Signals when a data correction event occurs
> 4 - L2 Cache Controller Signals when an uncorrectable data event occurs
>
> [...]
Added the impact of the bug & applied to dt-fixes, thanks!
[1/1] riscv: dts: microchip: correct L2 cache interrupts
https://git.kernel.org/conor/c/34fc9cc3aebe8b9
Thanks,
Conor.
next prev parent reply other threads:[~2022-08-18 20:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 13:25 [PATCH 1/1] riscv: dts: microchip: correct L2 cache interrupts Heinrich Schuchardt
2022-08-17 18:04 ` Conor.Dooley
2022-08-18 7:03 ` Daire.McNamara
2022-08-18 8:17 ` Heinrich Schuchardt
2022-08-18 8:33 ` Conor.Dooley
2022-08-18 20:19 ` Conor Dooley [this message]
2022-08-29 9:10 Heinrich Schuchardt
2022-08-29 10:32 ` Conor.Dooley
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=166085385179.1336923.6007777550886077496.b4-ty@microchip.com \
--to=mail@conchuod.ie \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@atishpatra.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=emil.renner.berthing@canonical.com \
--cc=geert@linux-m68k.org \
--cc=heinrich.schuchardt@canonical.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).