From: Jakub Kicinski <kuba@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: pull-request: wireless-2022-10-13
Date: Thu, 13 Oct 2022 08:32:54 -0700 [thread overview]
Message-ID: <20221013083254.5d302a5e@kernel.org> (raw)
In-Reply-To: <20221013100522.46346-1-johannes@sipsolutions.net>
On Thu, 13 Oct 2022 12:04:51 +0200 Johannes Berg wrote:
> Please pull and let me know if there's any problem.
Since you asked if there are any problems... :)
net/wireless/scan.c:1677:61: warning: incorrect type in argument 2 (different address spaces)
net/wireless/scan.c:1677:61: expected struct cfg80211_bss_ies const *new_ies
net/wireless/scan.c:1677:61: got struct cfg80211_bss_ies const [noderef] __rcu *beacon_ies
next prev parent reply other threads:[~2022-10-13 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 10:04 pull-request: wireless-2022-10-13 Johannes Berg
2022-10-13 15:32 ` Jakub Kicinski
2022-10-13 15:32 ` Jakub Kicinski [this message]
2022-10-13 16:13 ` Johannes Berg
2022-10-13 16:29 ` Jakub Kicinski
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=20221013083254.5d302a5e@kernel.org \
--to=kuba@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).