From: Johannes Berg <johannes@sipsolutions.net>
To: Chien Wong <m@xv97.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/6] wifi: mac80211: remove an unnecessary copy
Date: Mon, 10 Nov 2025 14:35:05 +0100 [thread overview]
Message-ID: <6a84990ab74953fff19daed71db79988f56a6fe5.camel@sipsolutions.net> (raw)
In-Reply-To: <0ed7eb21-a261-45b5-b3d2-9b9bb63d688d@xv97.com>
On Mon, 2025-11-10 at 21:33 +0800, Chien Wong wrote:
> On 11/10/25 3:34 PM, Johannes Berg wrote:
> > On Sun, 2025-11-09 at 22:04 +0800, Chien Wong wrote:
> > >
> > > Compile test only.
> >
> > You can trivially do better than that, say with hwsim + wlantest.
>
> OK. I will test with hwsim and update commit message in v2.
Or just remove that and add it in the cover letter, but anyway it seems
you _did_ even test it (to some extent) since you can't test just patch
6/6 by itself? :)
johannes
next prev parent reply other threads:[~2025-11-10 13:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-09 14:04 [PATCH 0/6] wifi: mac80211: refactor CMAC implementation Chien Wong
2025-11-09 14:04 ` [PATCH 1/6] wifi: mac80211: remove an unnecessary copy Chien Wong
2025-11-10 7:34 ` Johannes Berg
2025-11-10 13:33 ` Chien Wong
2025-11-10 13:35 ` Johannes Berg [this message]
2025-11-10 13:42 ` Chien Wong
2025-11-09 14:04 ` [PATCH 2/6] wifi: mac80211: fix CMAC functions not handling errors Chien Wong
2025-11-09 14:04 ` [PATCH 3/6] wifi: mac80211: add generic MMIE struct defines Chien Wong
2025-11-09 14:04 ` [PATCH 4/6] wifi: mac80211: utilize the newly defined CMAC constants Chien Wong
2025-11-09 14:04 ` [PATCH 5/6] wifi: mac80211: refactor CMAC crypt functions Chien Wong
2025-11-09 14:04 ` [PATCH 6/6] wifi: mac80211: refactor CMAC packet handlers Chien Wong
2025-11-10 7:43 ` Johannes Berg
2025-11-10 14:03 ` Chien Wong
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=6a84990ab74953fff19daed71db79988f56a6fe5.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=m@xv97.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