mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Rocco Folino <rocco@devzen.net>
Cc: kbuild-all@01.org, oleg.drokin@intel.com,
	andreas.dilger@intel.com, devel@driverdev.osuosl.org,
	dmiter4ever@gmail.com, arnd@arndb.de, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, Julia.Lawall@lip6.fr,
	Rocco Folino <rocco@devzen.net>,
	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, 3 Oct 2015 06:10:12 +0800	[thread overview]
Message-ID: <201510030633.j7jTVT5b%fengguang.wu@intel.com> (raw)
In-Reply-To: <a2bf5c53b3d03cf64edb2865b3eb01d52caaa6fc.1443821399.git.rocco@devzen.net>

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

Hi Rocco,

[auto build test results on v4.3-rc3 -- if it's inappropriate base, please ignore]

config: sparc64-allyesconfig (attached as .config)
reproduce:
        wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=sparc64 

All error/warnings (new ones prefixed by >>):

>> 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,
         ^

vim +/nrs_policy_get_info_locked +456 drivers/staging/lustre/lustre/ptlrpc/lproc_ptlrpc.c

   450	 *
   451	 * Information is copied in \a info.
   452	 *
   453	 * \param[in] policy The policy
   454	 * \param[out] info  Holds returned status information
   455	 */
 > 456	static void nrs_policy_get_info_locked(struct ptlrpc_nrs_policy *policy,
   457					struct ptlrpc_nrs_pol_info *info)
   458	{
   459		LASSERT(policy != NULL);

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 43733 bytes --]

  parent reply	other threads:[~2015-10-02 22:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 21:54 Rocco Folino
2015-10-02 21:59 ` Arnd Bergmann
2015-10-02 22:10 ` kbuild test robot [this message]
2015-10-02 22:13   ` Arnd Bergmann

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=201510030633.j7jTVT5b%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=Julia.Lawall@lip6.fr \
    --cc=andreas.dilger@intel.com \
    --cc=arnd@arndb.de \
    --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=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

all inboxes | Powered by JetHome®