mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Mario Limonciello <superm1@kernel.org>
Cc: Hans de Goede <hansg@kernel.org>, Ma Jun <Jun.Ma2@amd.com>,
	 Evan Quan <quanliangl@hotmail.com>,
	platform-driver-x86@vger.kernel.org,
	 LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] platform/x86/amd: send WBRF DSM payload as buffer
Date: Wed, 18 Nov 2026 21:56:42 +0200 (EET)	[thread overview]
Message-ID: <8161ce9b-ea0f-5a05-f99e-efbad38e2979@linux.intel.com> (raw)
In-Reply-To: <fa625e27-a1bd-4a22-8611-cca13fc9d11a@kernel.org>

On Wed, 18 Nov 2026, Mario Limonciello wrote:
> On 11/2/26 14:58, Mario Limonciello wrote:
> > Spec defines the WBRF record _DSM argument as a single buffer that packs
> > the header and frequency ranges. The driver instead built a package of
> > integers, so firmware on some systems abort \WBRF with AE_AML_OPERAND_TYPE
> > when dereferencing Arg2[0].
> > 
> > Encode the payload into a little-endian buffer and hand it as the lone
> > package element.
> > 
> > Fixes: 58e82a62669d ("platform/x86/amd: Add support for AMD ACPI based Wifi
> > band RFI mitigation feature")
> > Signed-off-by: Mario Limonciello <superm1@kernel.org>
> > ---
> > Changes in v2:
> > - Declare payload with __free(kfree) at the kzalloc() site, after input
> >    validation, instead of initializing it to NULL at the top of
> >    wbrf_record() (Sashiko)
> > - Compute payload length with struct_size_t() so it no longer depends on
> >    payload being declared earlier (Sashiko)
> > - Link to v1:
> > https://patch.msgid.link/20261102-superm1-wbrf-v1-1-b58d8d85277c@kernel.org
> 
> Ilpo,
> 
> FYI - this was found on some existing systems in the wild so I would prefer if
> it could go to -fixes.

Okay, thanks. I'll consider that once I get to processing patches once 
again.

> I sent right after the merge window so just wanted to make sure it's still in
> your queue.

Patchwork URL is in MAINTAINERS, though LLMs hitting it might have made 
only part of the queue visible to non-users.


-- 
 i.


      reply	other threads:[~2026-11-18 19:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-02 20:58 Mario Limonciello
2026-11-18 15:38 ` Mario Limonciello
2026-11-18 19:56   ` Ilpo Järvinen [this message]

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=8161ce9b-ea0f-5a05-f99e-efbad38e2979@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=Jun.Ma2@amd.com \
    --cc=hansg@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=quanliangl@hotmail.com \
    --cc=superm1@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

all inboxes | Powered by JetHome®