From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Baoyou Xie <baoyou.xie@linaro.org>
Cc: QLogic-Storage-Upstream@qlogic.com, jejb@linux.vnet.ibm.com,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, arnd@arndb.de,
xie.baoyou@zte.com.cn
Subject: Re: [PATCH] [SCSI] bnx2fc: mark symbols static where possible
Date: Fri, 09 Sep 2016 07:12:25 -0400 [thread overview]
Message-ID: <yq18tv1gwdi.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <1472971941-4882-1-git-send-email-baoyou.xie@linaro.org> (Baoyou Xie's message of "Sun, 4 Sep 2016 14:52:21 +0800")
>>>>> "Baoyou" == Baoyou Xie <baoyou.xie@linaro.org> writes:
Baoyou> We get a few warnings when building kernel with W=1:
Baoyou> drivers/scsi/bnx2fc/bnx2fc_els.c:257:6: warning: no previous
Baoyou> prototype for 'bnx2fc_srr_compl' [-Wmissing-prototypes]
Baoyou> drivers/scsi/bnx2fc/bnx2fc_els.c:367:6: warning: no previous
Baoyou> prototype for 'bnx2fc_rec_compl' [-Wmissing-prototypes]
Baoyou> drivers/scsi/bnx2fc/bnx2fc_fcoe.c:628:5: warning: no previous
Baoyou> prototype for 'bnx2fc_percpu_io_thread' [-Wmissing-prototypes]
Baoyou> drivers/scsi/bnx2fc/bnx2fc_fcoe.c:1413:26: warning: no previous
Baoyou> prototype for 'bnx2fc_interface_create' [-Wmissing-prototypes]
Baoyou> drivers/scsi/bnx2fc/bnx2fc_hwi.c:997:21: warning: no previous
Baoyou> prototype for 'bnx2fc_alloc_work' [-Wmissing-prototypes]
Baoyou> drivers/scsi/bnx2fc/bnx2fc_io.c:1082:5: warning: no previous
Baoyou> prototype for 'bnx2fc_abts_cleanup' [-Wmissing-prototypes] ....
Baoyou> In fact, these functions are only used in the file in which they
Baoyou> are declared and don't need a declaration, but can be made
Baoyou> static. so this patch marks these functions with 'static'.
Applied to 4.9/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2016-09-09 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 6:52 Baoyou Xie
2016-09-05 11:17 ` Arnd Bergmann
2016-09-08 14:51 ` Chad Dupuis
2016-09-09 11:12 ` Martin K. Petersen [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=yq18tv1gwdi.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=QLogic-Storage-Upstream@qlogic.com \
--cc=arnd@arndb.de \
--cc=baoyou.xie@linaro.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=xie.baoyou@zte.com.cn \
/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®