All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kalle Valo <kvalo@codeaurora.org>,
	Wireless <linux-wireless@vger.kernel.org>
Cc: Luca Coelho <luciano.coelho@intel.com>,
	Miri Korenblit <miriam.rachel.korenblit@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the wireless-drivers-next tree
Date: Thu, 24 Jun 2021 12:16:39 +1000	[thread overview]
Message-ID: <20210624121639.6d89a9b8@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 543 bytes --]

Hi all,

After merging the wireless-drivers-next tree, today's linux-next build
(x86_64 allmodconfig) produced this warning:

drivers/net/wireless/intel/iwlwifi/fw/acpi.c:720:12: warning: 'iwl_acpi_eval_dsm_func' defined but not used [-Wunused-function]
  720 | static u32 iwl_acpi_eval_dsm_func(struct device *dev, enum iwl_dsm_funcs_rev_0 eval_func)
      |            ^~~~~~~~~~~~~~~~~~~~~~

Introduced by commit

  7119f02b5d34 ("iwlwifi: mvm: support BIOS enable/disable for 11ax in Russia")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2021-06-24  2:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-24  2:16 Stephen Rothwell [this message]
2021-06-24  5:49 ` linux-next: build warning after merge of the wireless-drivers-next tree Kalle Valo
  -- strict thread matches above, loose matches on Subject: below --
2019-01-30 23:46 Stephen Rothwell
2019-01-30 23:51 ` Luca Coelho
2019-01-31 13:46   ` Kalle Valo
2019-01-31 13:46     ` Kalle Valo
2019-01-31 20:52     ` Stephen Rothwell
2017-01-13  0:12 Stephen Rothwell
2017-01-13 13:47 ` Kalle Valo
2017-01-17 11:49   ` Kalle Valo
2016-11-28  0:58 Stephen Rothwell
2016-11-28  7:25 ` Kalle Valo
2016-11-28  8:16   ` Barry Day
2016-11-28 11:44     ` Kalle Valo
2016-11-28 12:26       ` Jes Sorensen
2016-07-20  2:25 Stephen Rothwell
2016-07-20  2:25 ` Stephen Rothwell
2016-07-20  6:18 ` Reizer, Eyal
2016-07-20 18:41   ` Kalle Valo
2016-07-20 18:41     ` Kalle Valo
2016-07-08  1:32 Stephen Rothwell
2016-07-08  1:32 ` Stephen Rothwell
2016-07-08  1:35 ` Stephen Rothwell
2016-07-08  1:35   ` Stephen Rothwell

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=20210624121639.6d89a9b8@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luciano.coelho@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.