From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>,
Nathan Chancellor <nathan@kernel.org>
Cc: Mark Pearson <mpearson-lenovo@squebb.ca>,
"Derek J. Clark" <derekjohn.clark@gmail.com>,
Hans de Goede <hansg@kernel.org>, Armin Wolf <W_Armin@gmx.de>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Boqun Feng <boqun@kernel.org>, Waiman Long <longman@redhat.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: lenovo: wmi-gamezone: Drop gz_chain_head
Date: Tue, 17 Mar 2026 15:00:40 +0200 [thread overview]
Message-ID: <177375244084.9137.13371850428996047374.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20260313-lenovo-wmi-gamezone-remove-gz_chain_head-v1-1-ce5231f0c6fa@kernel.org>
On Fri, 13 Mar 2026 14:06:34 -0700, Nathan Chancellor wrote:
> After commit 1ea4b473504b ("locking/rwsem: Remove the list_head from
> struct rw_semaphore"), which removed a reference to the variable passed
> to __RWSEM_INITIALIZER(), certain configurations show an unused variable
> warning from the Lenovo wmi-gamezone driver:
>
> drivers/platform/x86/lenovo/wmi-gamezone.c:34:31: warning: 'gz_chain_head' defined but not used [-Wunused-variable]
> 34 | static BLOCKING_NOTIFIER_HEAD(gz_chain_head);
> | ^~~~~~~~~~~~~
> include/linux/notifier.h:119:39: note: in definition of macro 'BLOCKING_NOTIFIER_HEAD'
> 119 | struct blocking_notifier_head name = \
> | ^~~~
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-fixes branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-fixes branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/1] platform/x86: lenovo: wmi-gamezone: Drop gz_chain_head
commit: 6b99cc51e13e816962318e2f97e6ac58dc431c33
--
i.
prev parent reply other threads:[~2026-03-17 13:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 21:06 Nathan Chancellor
2026-03-14 18:27 ` Mark Pearson
2026-03-17 13:00 ` Ilpo Järvinen [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=177375244084.9137.13371850428996047374.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=W_Armin@gmx.de \
--cc=boqun@kernel.org \
--cc=derekjohn.clark@gmail.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=mpearson-lenovo@squebb.ca \
--cc=nathan@kernel.org \
--cc=peterz@infradead.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=will@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
all inboxes | Powered by JetHome®