[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240701130127.GA2250@willie-the-truck>
Date: Mon, 1 Jul 2024 14:01:27 +0100
From: Will Deacon <will@...nel.org>
To: Atish Patra <atishp@...osinc.com>
Cc: linux-riscv@...ts.infradead.org, kvm-riscv@...ts.infradead.org,
Atish Patra <atishp@...shpatra.org>,
Anup Patel <anup@...infault.org>,
Mark Rutland <mark.rutland@....com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Andrew Jones <ajones@...tanamicro.com>,
Conor Dooley <conor.dooley@...rochip.com>,
Samuel Holland <samuel.holland@...ive.com>,
Palmer Dabbelt <palmer@...osinc.com>,
Alexandre Ghiti <alexghiti@...osinc.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, garthlei@....edu.cn
Subject: Re: [PATCH v4 0/3] Assorted fixes in RISC-V PMU driver
On Fri, Jun 28, 2024 at 12:51:40AM -0700, Atish Patra wrote:
> This series contains 3 fixes out of which the first one is a new fix
> for invalid event data reported in lkml[2]. The last two are v3 of Samuel's
> patch[1]. I added the RB/TB/Fixes tag and moved 1 unrelated change
> to its own patch. I also changed an error message in kvm vcpu_pmu from
> pr_err to pr_debug to avoid redundant failure error messages generated
> due to the boot time quering of events implemented in the patch[1]
I'm assuming this series will go via the riscv arch tree, but please
shout if that's not the case.
Will
Powered by blists - more mailing lists