mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Jason Huang <Jason.Huang2@infineon.com>
Cc: linux-wireless@vger.kernel.org, brcm80211@lists.linux.dev,
	brcm80211-dev-list.pdl@broadcom.com,
	linux-kernel@vger.kernel.org,
	Arend van Spriel <arend.vanspriel@broadcom.com>
Subject: Re: [PATCH] wifi: brcmfmac: fix P2P action frame handling without device vif
Date: Sun,  2 Aug 2026 10:38:58 +0200	[thread overview]
Message-ID: <20260802083905.3819981-1-arend.vanspriel@broadcom.com> (raw)
In-Reply-To: <20260722082608.412472-1-Jason.Huang2@infineon.com>

On Wed, 22 Jul 2026 16:26:08 +0800, Jason Huang <Jason.Huang2@infineon.com> wrote:
> Some P2P action frame paths assume the P2P device vif is always
> available. That is not true when userspace sends non-P2P public action
> frames through the primary interface, or when action-frame abort runs
> after the P2P device vif has not been created.
>
> Fall back to the primary vif when aborting an action frame without a P2P
> device vif, and guard P2P device saved IE access before using it for
> peer channel search.
>
> Fixes: 30fb1b272909 ("brcmfmac: use actframe_abort to cancel ongoing action frame")
> Fixes: 6eda4e2c5425 ("brcmfmac: Add tx p2p off-channel support.")
>
> Signed-off-by: Jason Huang <jason.huang2@infineon.com>
> ---
>  drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c | 4 ++++
>  1 file changed, 4 insertions(+)

Acked-by: Arend van Spriel <arend.vanspriel@broadcom.com>

Provided Johannes is willing to fix the blank line once again. Fingers
crossed ;-)

Regards,
Arend

      parent reply	other threads:[~2026-08-02  8:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22  8:26 Jason Huang
2026-07-22  9:52 ` Johannes Berg
2026-08-02  8:38 ` Arend van Spriel [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=20260802083905.3819981-1-arend.vanspriel@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=Jason.Huang2@infineon.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=brcm80211@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@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

all inboxes | Powered by JetHome®