Linux wireless drivers development
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: HungTsung 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
Subject: Re: [PATCH v4] wifi: brcmfmac: add DPP support
Date: Mon, 20 Jul 2026 20:48:08 +0200	[thread overview]
Message-ID: <f9bcb849-cf98-4398-aa72-0b32885533fc@broadcom.com> (raw)
In-Reply-To: <20260715092229.GA667683@ISCN5CG5251XQT.infineon.com>

On 15/07/2026 11:22, HungTsung Huang wrote:
> 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.

Hi Jason,

I must have missed the "standalone P2P fix patch". Can you provide a 
reference or submit the patch against the wireless tree if not already 
done so.

Thanks,
Arend

  parent reply	other threads:[~2026-07-20 18:48 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
2026-07-15 18:46           ` Arend van Spriel
2026-07-20 18:48           ` Arend van Spriel [this message]
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=f9bcb849-cf98-4398-aa72-0b32885533fc@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