From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Jason Huang <Jason.Huang2@infineon.com>, linux-wireless@vger.kernel.org
Cc: wlan-kernel-dev-list@infineon.com
Subject: Re: [PATCH v2 0/2] wifi: support authorized roaming offload reporting
Date: Wed, 5 Aug 2026 15:22:57 -0700 [thread overview]
Message-ID: <39262e9c-e41c-49d3-9b95-6aeb81d2e864@oss.qualcomm.com> (raw)
In-Reply-To: <20260805110116.35884-1-Jason.Huang2@infineon.com>
On 8/5/2026 4:01 AM, Jason Huang wrote:
> From: Jason Huang <jason.huang2@infineon.com>
>
> This is a shorter resend of the cfg80211/nl80211 API patches from the
> previous 7-patch series. The earlier submission appears to have been
> partially processed, so resend only these two prerequisite patches as a
> standalone series.
>
> The series lets drivers report connect and roam events that are already
> authorized by firmware offload, and adds a roam offload extended feature
> so userspace can provide PMK material for FT/OKC roaming offload without
> requiring full 802.1X 4-way handshake offload support.
>
> Changes in v2:
> - Resend as a shorter 2-patch series for nipa processing.
> - No code changes
>
> Jason Huang (2):
> wifi: cfg80211: report authorized connect and roam events
> wifi: nl80211: add roam offload extended feature
>
> include/net/cfg80211.h | 6 ++++++
> include/uapi/linux/nl80211.h | 8 +++++++-
> net/wireless/nl80211.c | 10 ++++++++--
> net/wireless/sme.c | 2 ++
> 4 files changed, 23 insertions(+), 3 deletions(-)
>
>
> base-commit: 6c5fc504d0d6934132637aa3db4b9b58148eaa78
You need to figure out your patch posting.
You posted a v2 cover letter as a separate thread (which is correct), but
without the two actual patches.
https://lore.kernel.org/all/20260805105716.35643-1-Jason.Huang2@infineon.com/
You then posted a v2 cover letter with the 2 patches, but as a reply to the V1
which is not correct. The new version should have been a separate thread.
https://lore.kernel.org/all/20260805110116.35884-1-Jason.Huang2@infineon.com/
(has In-Reply-To: <20260804030450.232028-1-Jason.Huang2@infineon.com>)
If you are new to posting then I strongly suggest using 'b4' to post patches
since it takes care of almost all of these details for you.
/jeff
next prev parent reply other threads:[~2026-08-05 22:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 3:04 [PATCH 1/7] wifi: cfg80211: report authorized connect and roam events Jason Huang
2026-08-04 3:04 ` [PATCH 2/7] wifi: nl80211: add roam offload extended feature Jason Huang
2026-08-04 6:43 ` [PATCH 1/7] wifi: cfg80211: report authorized connect and roam events Johannes Berg
2026-08-05 11:01 ` [PATCH v2 0/2] wifi: support authorized roaming offload reporting Jason Huang
2026-08-05 11:01 ` [PATCH v2 1/2] wifi: cfg80211: report authorized connect and roam events Jason Huang
2026-08-05 22:50 ` Jeff Johnson
2026-08-06 4:03 ` HungTsung Huang
2026-08-05 11:01 ` [PATCH v2 2/2] wifi: nl80211: add roam offload extended feature Jason Huang
2026-08-05 22:22 ` Jeff Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-05 10:57 [PATCH v2 0/2] wifi: support authorized roaming offload reporting Jason Huang
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=39262e9c-e41c-49d3-9b95-6aeb81d2e864@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=Jason.Huang2@infineon.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wlan-kernel-dev-list@infineon.com \
/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