From: Arnd Bergmann <arnd@arndb.de>
To: kbuild test robot <lkp@intel.com>
Cc: Rocco Folino <rocco@devzen.net>,
kbuild-all@01.org, oleg.drokin@intel.com,
andreas.dilger@intel.com, devel@driverdev.osuosl.org,
dmiter4ever@gmail.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, Julia.Lawall@lip6.fr,
hannac@iu.edu, joe@perches.com, lustre-devel@lists.lustre.org
Subject: Re: [PATCH] staging/lustre: Make nrs_policy_get_info_locked() static
Date: Sat, 03 Oct 2015 00:13:33 +0200 [thread overview]
Message-ID: <5223334.NTtjKnhML6@wuerfel> (raw)
In-Reply-To: <201510030633.j7jTVT5b%fengguang.wu@intel.com>
On Saturday 03 October 2015 06:10:12 kbuild test robot wrote:
> >> drivers/staging/lustre/lustre/ptlrpc/lproc_ptlrpc.c:456:13: error: static declaration of 'nrs_policy_get_info_locked' follows non-static declaration
> static void nrs_policy_get_info_locked(struct ptlrpc_nrs_policy *policy,
> ^
> In file included from drivers/staging/lustre/lustre/ptlrpc/../include/lustre_lib.h:64:0,
> from drivers/staging/lustre/lustre/ptlrpc/../include/obd.h:52,
> from drivers/staging/lustre/lustre/ptlrpc/lproc_ptlrpc.c:40:
> drivers/staging/lustre/lustre/ptlrpc/../include/lustre_net.h:1542:6: note: previous declaration of 'nrs_policy_get_info_locked' was here
> void nrs_policy_get_info_locked(struct ptlrpc_nrs_policy *policy,
> ^
>
fwiw, the patch should be fine on staging-testing, just not on mainline at the moment.
Arnd
prev parent reply other threads:[~2015-10-02 22:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 21:54 [PATCH] staging/lustre: Make nrs_policy_get_info_locked() static Rocco Folino
2015-10-02 21:59 ` Arnd Bergmann
2015-10-02 22:10 ` kbuild test robot
2015-10-02 22:13 ` Arnd Bergmann [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=5223334.NTtjKnhML6@wuerfel \
--to=arnd@arndb.de \
--cc=Julia.Lawall@lip6.fr \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=dmiter4ever@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hannac@iu.edu \
--cc=joe@perches.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lustre-devel@lists.lustre.org \
--cc=oleg.drokin@intel.com \
--cc=rocco@devzen.net \
/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