Linux wireless drivers development
 help / color / mirror / Atom feed
From: HungTsung Huang <Jason.Huang2@infineon.com>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: <linux-wireless@vger.kernel.org>, <brcm80211@lists.linux.dev>,
	<brcm80211-dev-list.pdl@broadcom.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] wifi: brcmfmac: add DPP support
Date: Wed, 15 Jul 2026 17:22:29 +0800	[thread overview]
Message-ID: <20260715092229.GA667683@ISCN5CG5251XQT.infineon.com> (raw)
In-Reply-To: <20260712223314.2182929-1-arend.vanspriel@broadcom.com>

Hi Arend,

Thanks for the clarification.

Could you please confirm whether it is OK to submit the standalone P2P fix
to wireless in parallel to wireless-next origin/main? My understanding is
that the P2P fix does not need to wait for the DPP support patch to be
accepted, since it fixes pre-existing bugs and the DPP patch no longer
depends on it.

The reason I added:
> > +         p2p->bss_idx[P2PAPI_BSSCFG_DEVICE].vif &&
> >           p2p->bss_idx[P2PAPI_BSSCFG_DEVICE].vif->saved_ie.probe_req_ie_len) {

was that DPP public action frames can be sent through the primary interface
without a P2P device vif being created. The existing peer channel search path
assumed the P2P device vif was always available before accessing saved
Probe Request IEs, which could dereference a NULL vif in that case. However,
I agree this is a pre-existing P2P bug rather than part of DPP support, so I
moved it into the standalone P2P fix patch.

Regards,
Jason

  reply	other threads:[~2026-07-15  9:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03  3:57 [PATCH] wifi: brcmfmac: add DPP support and fix fw-supplicant/P2P interop Jason Huang
2026-06-03 13:20 ` kernel test robot
2026-06-04  3:42 ` [PATCH v2] " Jason Huang
2026-07-06 10:25   ` Arend van Spriel
2026-07-08  3:58   ` [PATCH v3] wifi: brcmfmac: add DPP support Jason Huang
2026-07-08  7:12     ` [PATCH v4] " Jason Huang
2026-07-12 22:33       ` Arend van Spriel
2026-07-15  9:22         ` HungTsung Huang [this message]
2026-07-15 18:46           ` Arend van Spriel
2026-07-20 18:48           ` Arend van Spriel
2026-07-15  8:47       ` [PATCH v5] " Jason Huang
2026-07-20 19:48         ` Arend van Spriel

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=20260715092229.GA667683@ISCN5CG5251XQT.infineon.com \
    --to=jason.huang2@infineon.com \
    --cc=arend.vanspriel@broadcom.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