From: Johannes Berg <johannes@sipsolutions.net>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
Kalle Valo <kvalo@kernel.org>
Subject: Re: pull-request: wireless-next-2023-03-16
Date: Thu, 16 Feb 2023 20:49:04 +0100 [thread overview]
Message-ID: <fbae8518cdb529e175ee771bdd288bd64858f67c.camel@sipsolutions.net> (raw)
In-Reply-To: <20230216113253.2cbb360e@kernel.org>
On Thu, 2023-02-16 at 11:32 -0800, Jakub Kicinski wrote:
> 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?
Huh, yes, sorry about that.
> 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)
> ^
>
That's particularly odd, feels like that was already unused since (my)
commit 3a894a9f319f ("iwlwifi: remove TOF implementation")? But that's
_ancient_.
So I think probably the new ones are different than that one, how did
you find this one?
Anyway there are far too many left ...
johannes
next prev parent reply other threads:[~2023-02-16 19:49 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
2023-02-16 19:49 ` Johannes Berg [this message]
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=fbae8518cdb529e175ee771bdd288bd64858f67c.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--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).