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-next-2023-03-16
Date: Thu, 16 Feb 2023 11:32:53 -0800 [thread overview]
Message-ID: <20230216113253.2cbb360e@kernel.org> (raw)
In-Reply-To: <20230216105406.208416-1-johannes@sipsolutions.net>
On Thu, 16 Feb 2023 11:54:05 +0100 Johannes Berg wrote:
> Here's a last (obviously) set of new work for -next. The
> major changes are summarized in the tag below.
>
> Please pull and let me know if there's any problem.
Could you follow up soon with fixes for the compilation warnings?
drivers/net/wireless/intel/iwlwifi/mvm/debugfs-vif.c:441:21: warning: unused function 'iwl_dbgfs_is_match' [-Wunused-function]
static inline char *iwl_dbgfs_is_match(char *name, char *buf)
^
there are also 2 new fortify string warnings (could be false positives).
next prev parent reply other threads:[~2023-02-16 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 10:54 pull-request: wireless-next-2023-03-16 Johannes Berg
2023-02-16 19:32 ` Jakub Kicinski [this message]
2023-02-16 19:49 ` Johannes Berg
2023-02-16 19:40 ` patchwork-bot+netdevbpf
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=20230216113253.2cbb360e@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).