From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Cc: Miri Korenblit <miriam.rachel.korenblit@intel.com>,
Ilan Peer <ilan.peer@intel.com>
Subject: Re: [PATCH] wifi: cfg80211: fix 6 GHz scan request building
Date: Fri, 10 May 2024 11:36:33 +0200 [thread overview]
Message-ID: <113b4bbf58565fcc84db0ef04338aef9eeb0d2f0.camel@sipsolutions.net> (raw)
In-Reply-To: <20240510113244.b5f4ef741cc6.I0cb19188be17a8abd029805e3373c0a7777c214c@changeid>
On Fri, 2024-05-10 at 11:32 +0200, Johannes Berg wrote:
> From: Miri Korenblit <miriam.rachel.korenblit@intel.com>
>
Huh, I didn't mean to add that there, sorry. I have to take
responsibility for almost all of this, just squashed in a little thing
from Miri about the SSIDs pointer being NULL when n_ssids is 0.
johannes
prev parent reply other threads:[~2024-05-10 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 9:32 [PATCH] wifi: cfg80211: fix 6 GHz scan request building Johannes Berg
2024-05-10 9:36 ` Johannes Berg [this message]
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=113b4bbf58565fcc84db0ef04338aef9eeb0d2f0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ilan.peer@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).