[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMj1kXGSNT08QrCp1jazmi9ANpZ7RCuS4kHo9x6hwxtp6z0Nhg@mail.gmail.com>
Date: Sat, 21 Jun 2025 10:15:52 +0200
From: Ard Biesheuvel <ardb@...nel.org>
To: Daniel Ferguson <danielf@...amperecomputing.com>
Cc: Borislav Petkov <bp@...en8.de>, Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
James Morse <james.morse@....com>, Jonathan Corbet <corbet@....net>, Tony Luck <tony.luck@...el.com>,
linux-acpi@...r.kernel.org, linux-doc@...r.kernel.org,
linux-edac@...r.kernel.org, linux-efi@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/5] Fix issues with ARM Processor CPER records
On Fri, 6 Jun 2025 at 20:30, Daniel Ferguson
<danielf@...amperecomputing.com> wrote:
>
>
>
> On 10/14/2024 3:00 AM, Ard Biesheuvel wrote:
> > On Fri, 11 Oct 2024 at 13:57, Borislav Petkov <bp@...en8.de> wrote:
> >>
> >> On Wed, Sep 04, 2024 at 08:07:13AM +0200, Mauro Carvalho Chehab wrote:
> >>> Jason Tian (1):
> >>> RAS: Report all ARM processor CPER information to userspace
> >>>
> >>> Mauro Carvalho Chehab (4):
> >>> efi/cper: Adjust infopfx size to accept an extra space
> >>> efi/cper: Add a new helper function to print bitmasks
> >>> efi/cper: align ARM CPER type with UEFI 2.9A/2.10 specs
> >>> docs: efi: add CPER functions to driver-api
> >>>
> >>> .../driver-api/firmware/efi/index.rst | 11 +++-
> >>> drivers/acpi/apei/ghes.c | 27 ++++----
> >>> drivers/firmware/efi/cper-arm.c | 52 ++++++++--------
> >>> drivers/firmware/efi/cper.c | 62 ++++++++++++++++++-
> >>> drivers/ras/ras.c | 41 +++++++++++-
> >>> include/linux/cper.h | 12 ++--
> >>> include/linux/ras.h | 16 ++++-
> >>> include/ras/ras_event.h | 48 ++++++++++++--
> >>> 8 files changed, 210 insertions(+), 59 deletions(-)
> >>
> >> With the issues to patch 1 fixed:
> >>
> >> Acked-by: Borislav Petkov (AMD) <bp@...en8.de>
> >>
> >> I'm presuming this'll go through Ard's tree. Alternatively, I can pick it up
> >> too with Ard's ack.
> >>
> >
> > Either works for me.
> >
> > Mauro: please put all maintainers on cc of the code you are touching - thanks.
>
> What can I do to help this patch move forward?
> I noticed it needs to be rebased as of kernel v6.15.
>
> Would it be helpful if I were to rebase, add all the maintainers to the cc, and
> resubmit ?
>
Yes, please. And make sure you incorporate Boris's feedback on patch
#1 and apply his conditional ack.
Thanks,
Powered by blists - more mailing lists