From: Arnd Bergmann <arnd@arndb.de>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Anil Gurumurthy <anil.gurumurthy@qlogic.com>,
Sudarsana Kalluru <sudarsana.kalluru@qlogic.com>,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Baoyou Xie <baoyou.xie@linaro.org>
Subject: Re: [PATCH 1/5] bfa: mark symbols static where possible
Date: Wed, 03 Aug 2016 09:46:01 +0200 [thread overview]
Message-ID: <4472099.0XASieJnNU@wuerfel> (raw)
In-Reply-To: <201608031208.Y8UqZJYW%fengguang.wu@intel.com>
On Wednesday, August 3, 2016 12:45:50 PM CEST kbuild test robot wrote:
> All errors (new ones prefixed by >>):
>
> drivers/scsi/bfa/bfad.c: In function 'bfad_drv_uninit':
> >> drivers/scsi/bfa/bfad.c:888:2: error: implicit declaration of function 'bfa_isr_disable' [-Werror=implicit-function-declaration]
> bfa_isr_disable(&bfad->bfa);
> ^
> cc1: some warnings being treated as errors
>
Ah right: This is called in a function that gets removed in patch 5,
after which it is actually local. I made a mistake here when I went
through a repeated search for local functions.
I'll wait for other comments first before I send a fixed version.
Arnd
next prev parent reply other threads:[~2016-08-03 7:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 15:22 [PATCH 0/5] bfa: fix W=1 build warnings Arnd Bergmann
2016-08-02 15:22 ` [PATCH 1/5] bfa: mark symbols static where possible Arnd Bergmann
2016-08-03 4:45 ` kbuild test robot
2016-08-03 7:46 ` Arnd Bergmann [this message]
2016-08-10 5:20 ` Sudarsana Kalluru
2016-08-02 15:22 ` [PATCH 2/5] bfa: remove unused variables Arnd Bergmann
2016-08-02 15:22 ` [PATCH 3/5] bfa: rename some global variables Arnd Bergmann
2016-08-02 15:22 ` [PATCH 4/5] bfa: remove unused functions from fbbuild.c Arnd Bergmann
2016-08-02 15:22 ` [PATCH 5/5] bfa: remove more unused functions Arnd Bergmann
2016-08-10 5:28 ` [PATCH 0/5] bfa: fix W=1 build warnings Sudarsana Kalluru
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=4472099.0XASieJnNU@wuerfel \
--to=arnd@arndb.de \
--cc=anil.gurumurthy@qlogic.com \
--cc=baoyou.xie@linaro.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lkp@intel.com \
--cc=martin.petersen@oracle.com \
--cc=sudarsana.kalluru@qlogic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox