[martinbrandenburg:for-next 20/24] fs/orangefs/file.c:586:5: sparse: symbol 'orangefs_flush' was not declared. Should it be static?

mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed

From: kbuild test robot <fengguang.wu@intel.com>
To: Martin Brandenburg <martin@omnibond.com>
Cc: kbuild-all@01.org, Mike Marshall <hubcap@omnibond.com>,
	devel@lists.orangefs.org, linux-kernel@vger.kernel.org
Subject: [martinbrandenburg:for-next 20/24] fs/orangefs/file.c:586:5: sparse: symbol 'orangefs_flush' was not declared. Should it be static?
Date: Fri, 16 Mar 2018 16:15:33 +0800	[thread overview]
Message-ID: <201803161633.LJb0owl8%fengguang.wu@intel.com> (raw)

tree:   https://github.com/martinbrandenburg/linux for-next
head:   f73753424e408389a77bcfa9b04beb41f0f6b2f8
commit: 27dd09ddfeca4937da105e89ded1ba3d35e1038e [20/24] orangefs: implement writepage
reproduce:
        # apt-get install sparse
        git checkout 27dd09ddfeca4937da105e89ded1ba3d35e1038e
        make ARCH=x86_64 allmodconfig
        make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

   fs/orangefs/file.c:428:35: sparse: symbol 'orangefs_file_vm_ops' was not declared. Should it be static?
>> fs/orangefs/file.c:586:5: sparse: symbol 'orangefs_flush' was not declared. Should it be static?
--
>> fs/orangefs/inode.c:88:5: sparse: symbol 'orangefs_write_end' was not declared. Should it be static?

Please review and possibly fold the followup patch.

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

next             reply	other threads:[~2018-03-16  8:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16  8:15 kbuild test robot [this message]
2018-03-16  8:15 ` [RFC PATCH martinbrandenburg] orangefs: orangefs_write_end() can be static kbuild test robot

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=201803161633.LJb0owl8%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=devel@lists.orangefs.org \
    --cc=hubcap@omnibond.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@omnibond.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

all inboxes | Powered by JetHome®