From: Bjorn Helgaas <bhelgaas@google.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next list <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
poza@codeaurora.org
Subject: Re: linux-next: build warnings after merge of the pci tree
Date: Tue, 2 Oct 2018 08:47:37 -0500 [thread overview]
Message-ID: <CAErSpo52h3KEFvEw+dEGiy53uvD=956K8QT5RQFLk=ArDJ9EUw@mail.gmail.com> (raw)
In-Reply-To: <20181002102602.53320db6@canb.auug.org.au>
On Mon, Oct 1, 2018 at 7:26 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi Bjorn,
>
> After merging the pci tree, today's linux-next build (powerpc
> ppc64_defconfig) produced these warning:
>
> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c: In function 'ixgbe_io_slot_reset':
> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c:11102:6: warning: unused variable 'err' [-Wunused-variable]
> int err;
> ^~~
> drivers/net/ethernet/intel/i40e/i40e_main.c: In function 'i40e_pci_error_slot_reset':
> drivers/net/ethernet/intel/i40e/i40e_main.c:14230:6: warning: unused variable 'err' [-Wunused-variable]
> int err;
> ^~~
>
> also from the x86_64 allmodconfig build:
>
> drivers/dma/ioat/init.c: In function 'ioat_pcie_error_slot_reset':
> drivers/dma/ioat/init.c:1255:6: warning: unused variable 'err' [-Wunused-variable]
> int err;
> ^~~
> drivers/net/ethernet/sfc/efx.c: In function 'efx_io_slot_reset':
> drivers/net/ethernet/sfc/efx.c:3824:6: warning: unused variable 'rc' [-Wunused-variable]
> int rc;
> ^~
> drivers/net/ethernet/sfc/falcon/efx.c: In function 'ef4_io_slot_reset':
> drivers/net/ethernet/sfc/falcon/efx.c:3163:6: warning: unused variable 'rc' [-Wunused-variable]
> int rc;
> ^~
Fixed the above, thanks!
> Introduced by commit
>
> 6dcde3e574b2 ("XXX PCI/AER: Remove pci_cleanup_aer_uncorrect_error_status() calls")
> (good subject prefix there :-))
Yeah, that's a note to self to update something in the changelog.
Bjorn
next prev parent reply other threads:[~2018-10-02 13:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 0:26 linux-next: build warnings after merge of the pci tree Stephen Rothwell
2018-10-02 13:47 ` Bjorn Helgaas [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-05 5:09 Stephen Rothwell
2024-02-06 20:21 ` Philipp Stanner
2022-03-01 2:59 Stephen Rothwell
2022-03-01 15:01 ` Bjorn Helgaas
2016-06-20 1:52 Stephen Rothwell
2016-06-20 19:11 ` Bjorn Helgaas
2016-06-21 1:08 ` Stephen Rothwell
2016-06-21 1:27 ` Bjorn Helgaas
[not found] <EDA0A4495861324DA2618B4C45DCB3EE612CE1@blrx3m08.blr.amer.dell.com>
2010-08-02 12:44 ` Narendra K
2010-08-02 1:18 Stephen Rothwell
2010-08-02 1:38 ` 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='CAErSpo52h3KEFvEw+dEGiy53uvD=956K8QT5RQFLk=ArDJ9EUw@mail.gmail.com' \
--to=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=poza@codeaurora.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).