linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Mike Marshall <hubcap@omnibond.com>
Cc: kbuild-all@01.org, Martin Brandenburg <martin@omnibond.com>,
	devel@lists.orangefs.org, linux-kernel@vger.kernel.org
Subject: [hubcap:for-next 20/22] fs/orangefs/file.c:574:5: sparse: symbol 'orangefs_file_open' was not declared. Should it be static?
Date: Thu, 11 Apr 2019 09:58:50 +0800	[thread overview]
Message-ID: <201904110915.9jPFP0Co%lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux for-next
head:   6055a739910e69f8f76120d48e7ae74a13b1fdda
commit: 9a959aaffd7090810eade53e4d960614405f57c6 [20/22] orangefs: remember count when reading.
reproduce:
        # apt-get install sparse
        git checkout 9a959aaffd7090810eade53e4d960614405f57c6
        make ARCH=x86_64 allmodconfig
        make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'


sparse warnings: (new ones prefixed by >>)

>> fs/orangefs/file.c:574:5: sparse: symbol 'orangefs_file_open' was not declared. Should it be static?
   fs/orangefs/file.c:580:5: sparse: symbol 'orangefs_flush' 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

             reply	other threads:[~2019-04-11  1:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11  1:58 kbuild test robot [this message]
2019-04-11  1:58 ` [RFC PATCH hubcap] orangefs: orangefs_file_open() can be static kbuild test robot
2019-04-11  2:15   ` Joe Perches

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=201904110915.9jPFP0Co%lkp@intel.com \
    --to=lkp@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;
as well as URLs for NNTP newsgroup(s).