Linux wireless drivers development
 help / color / mirror / Atom feed
From: HungTsung Huang <Jason.Huang2@infineon.com>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>,
	<wlan-kernel-dev-list@infineon.com>,
	Chung-Hsien Hsu <Chung-Hsien.Hsu@infineon.com>,
	Chi-hsien Lin <chi-hsien.lin@cypress.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] wifi: cfg80211: report authorized connect and roam events
Date: Thu, 6 Aug 2026 12:03:22 +0800	[thread overview]
Message-ID: <20260806040304.GA39624@ISCN5CG5251XQT.infineon.com> (raw)
In-Reply-To: <f2c8c83f-e2e4-4ed1-871f-f1bb1d71c057@oss.qualcomm.com>

Thanks for your review.
> > Assisted-by: GitHub Copilot CLI:gpt-5.5
> > Signed-off-by: Chung-Hsien Hsu <Chung-Hsien.Hsu@infineon.com>
> > Signed-off-by: Chi-hsien Lin <chi-hsien.lin@cypress.com> 
To clarify the roles for this patch:
- Chung-Hsien Hsu is the original author of the code.
- Chi-hsien Lin supervised and reviewed the development.
- I am responsible for refactoring, testing, and submitting this patch.

I apologize for the confusion in the sign-off chain. I will fix the patch
attribution in v3 by setting Chung-Hsien as the From/Author and will make
sure the Signed-off-by order to reflect the delivery path correctly.

> This attribute became deprecated when NL80211_CMD_PORT_AUTHORIZED was
> introduced. Why are you not using that?
> 
> 503c1fb98ba3 ("cfg80211/nl80211: add a port authorized event")
> 
You are right. I will drop this cfg80211/nl80211 change in v3 and use the
existing port-authorized event model instead.

  reply	other threads:[~2026-08-06  4:03 UTC|newest]

Thread overview: 9+ 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 [this message]
2026-08-05 11:01   ` [PATCH v2 2/2] wifi: nl80211: add roam offload extended feature Jason Huang
2026-08-05 22:22   ` [PATCH v2 0/2] wifi: support authorized roaming offload reporting Jeff Johnson

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=20260806040304.GA39624@ISCN5CG5251XQT.infineon.com \
    --to=jason.huang2@infineon.com \
    --cc=Chung-Hsien.Hsu@infineon.com \
    --cc=chi-hsien.lin@cypress.com \
    --cc=jeff.johnson@oss.qualcomm.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --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