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: [RFC PATCH hubcap] orangefs: orangefs_file_open() can be static
Date: Thu, 11 Apr 2019 09:58:50 +0800 [thread overview]
Message-ID: <20190411015850.GA10504@lkp-wsm-ep1> (raw)
In-Reply-To: <201904110915.9jPFP0Co%lkp@intel.com>
Fixes: 9a959aaffd70 ("orangefs: remember count when reading.")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
file.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/orangefs/file.c b/fs/orangefs/file.c
index d198af9..01d0db6 100644
--- a/fs/orangefs/file.c
+++ b/fs/orangefs/file.c
@@ -571,7 +571,7 @@ static int orangefs_lock(struct file *filp, int cmd, struct file_lock *fl)
return rc;
}
-int orangefs_file_open(struct inode * inode, struct file *file)
+static int orangefs_file_open(struct inode * inode, struct file *file)
{
file->private_data = NULL;
return generic_file_open(inode, file);
next prev parent reply other threads:[~2019-04-11 1:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 1:58 [hubcap:for-next 20/22] fs/orangefs/file.c:574:5: sparse: symbol 'orangefs_file_open' was not declared. Should it be static? kbuild test robot
2019-04-11 1:58 ` kbuild test robot [this message]
2019-04-11 2:15 ` [RFC PATCH hubcap] orangefs: orangefs_file_open() can be static 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=20190411015850.GA10504@lkp-wsm-ep1 \
--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).