[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJZ5v0hFb_SMYvbEuWJt2cfzYxAwAyUfAvWKwNaae_hz+Bj==w@mail.gmail.com>
Date: Mon, 27 Oct 2025 20:38:35 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: "Luck, Tony" <tony.luck@...el.com>
Cc: "Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"patches@...ts.linux.dev" <patches@...ts.linux.dev>
Subject: Re: [PATCH] ACPI: MRRM: Check revision of MRRM table
On Thu, Oct 23, 2025 at 6:01 PM Rafael J. Wysocki <rafael@...nel.org> wrote:
>
> On Thu, Oct 23, 2025 at 5:56 PM Luck, Tony <tony.luck@...el.com> wrote:
> >
> > >> Before trying to parse the MRRM table, check that the table revision
> > >> is the one that is expected.
> > >
> > > OK, so should there be a Fixes: tag? Or is it just a tidy-up of the code?
> >
> > I'd be surprised if this table changed. But the h/w team that proposed the
> > MRRM table nagged me to check the revision "just in case". Which seems
> > like good practice.
> >
> > Might as well add a Fixes to get this back ported in case someone locks onto
> > v6.16 or v6.17.
> >
> > Fixes: b9020bdb9f76 ("ACPI: MRRM: Minimal parse of ACPI MRRM table")
> >
> > Would you like me to post a V2, or can you just edit this in as you apply?
>
> No worries, I can edit it.
Applied with the Fixed: tag added as 6.18-rc material, thanks!
Powered by blists - more mailing lists