public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Bjorn Helgaas <bhelgaas@google•com>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Oza Pawandeep <poza@codeaurora•org>
Subject: linux-next: build warnings after merge of the pci tree
Date: Tue, 2 Oct 2018 10:26:02 +1000	[thread overview]
Message-ID: <20181002102602.53320db6@canb.auug.org.au> (raw)

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

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;
      ^~

Introduced by commit

  6dcde3e574b2 ("XXX PCI/AER: Remove pci_cleanup_aer_uncorrect_error_status() calls")
(good subject prefix there :-))


-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2018-10-02  0:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-02  0:26 Stephen Rothwell [this message]
2018-10-02 13:47 ` linux-next: build warnings after merge of the pci tree Bjorn Helgaas
  -- strict thread matches above, loose matches on Subject: below --
2026-01-05  5:00 Stephen Rothwell
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=20181002102602.53320db6@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=bhelgaas@google$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=poza@codeaurora$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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