linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	 Linux Next Mailing List <linux-next@vger.kernel.org>,
	 Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	 linux-pci@vger.kernel.org
Subject: Re: linux-next: Tree for May 5 (drivers/pci/pcie/bwctrl.c)
Date: Tue, 6 May 2025 14:25:51 +0300 (EEST)	[thread overview]
Message-ID: <cbd7bfaf-613e-631b-db39-b63864049f4b@linux.intel.com> (raw)
In-Reply-To: <0ab5fe5d-feda-4a3a-8803-92eb4e52e3b4@infradead.org>

On Mon, 5 May 2025, Randy Dunlap wrote:

> 
> 
> On 5/5/25 1:41 AM, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20250502:
> > 
> 
> on x86_64:
> 
> drivers/pci/pcie/bwctrl.c:56:22: warning: 'pcie_bwctrl_lbms_rwsem' defined but not used [-Wunused-variable]
>    56 | static DECLARE_RWSEM(pcie_bwctrl_lbms_rwsem);
>       |                      ^~~~~~~~~~~~~~~~~~~~~~
> include/linux/rwsem.h:153:29: note: in definition of macro 'DECLARE_RWSEM'
>   153 |         struct rw_semaphore lockname = __RWSEM_INITIALIZER(lockname)
>       |                             ^~~~~~~~

Thank for the heads up, I don't know what I was thinking. I remove all 
code related to that rwsem but forgot to remove the rwsem itself. I'll 
send a patch once our build tester has had the opportunity to check it.

-- 
 i.


      reply	other threads:[~2025-05-06 11:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-05  8:41 linux-next: Tree for May 5 Stephen Rothwell
2025-05-05 23:31 ` linux-next: Tree for May 5 (drivers/pci/pcie/bwctrl.c) Randy Dunlap
2025-05-06 11:25   ` 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=cbd7bfaf-613e-631b-db39-b63864049f4b@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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).