linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: kbuild-all@lists.01.org, linux-fsdevel@vger.kernel.org,
	David Howells <dhowells@redhat.com>,
	Christian Brauner <christian@brauner.io>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	Miklos Szeredi <miklos@szeredi.hu>
Subject: [RFC PATCH] configfd: configfd_context_fops can be static
Date: Mon, 6 Jan 2020 11:58:30 +0800	[thread overview]
Message-ID: <20200106035830.6ok7ehpfcenns2hl@f53c9c00458a> (raw)
In-Reply-To: <20200104201432.27320-3-James.Bottomley@HansenPartnership.com>


Fixes: 74148c8fa2fc ("configfd: add generic file descriptor based configuration parser")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
 configfd.c |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/fs/configfd.c b/fs/configfd.c
index 7f2c750ac7e30..a0ca741718704 100644
--- a/fs/configfd.c
+++ b/fs/configfd.c
@@ -50,7 +50,7 @@ static int configfd_release(struct inode *inode, struct file *file)
 	return 0;
 }
 
-const struct file_operations configfd_context_fops = {
+static const struct file_operations configfd_context_fops = {
 	.read		= configfd_read,
 	.release	= configfd_release,
 	.llseek		= no_llseek,
@@ -93,8 +93,8 @@ static struct configfd_type *configfd_type_get(const char *name)
 	return cft;
 }
 
-struct configfd_context *configfd_context_alloc(const struct configfd_type *cft,
-						unsigned int op)
+static struct configfd_context *configfd_context_alloc(const struct configfd_type *cft,
+						       unsigned int op)
 {
 	struct configfd_context *cfc;
 	struct logger *log;

  parent reply	other threads:[~2020-01-06  3:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-04 20:14 [PATCH v2 0/6] introduce configfd as generalisation of fsconfig James Bottomley
2020-01-04 20:14 ` [PATCH v2 1/6] logger: add a limited buffer logging facility James Bottomley
2020-01-04 20:14 ` [PATCH v2 2/6] configfd: add generic file descriptor based configuration parser James Bottomley
2020-01-06  3:58   ` kbuild test robot
2020-01-06  3:58   ` kbuild test robot [this message]
2020-01-04 20:14 ` [PATCH v2 3/6] configfd: syscall: wire up configfd syscalls James Bottomley
2020-01-04 20:14 ` [PATCH v2 4/6] fs: implement fsconfig via configfd James Bottomley
2020-01-05  1:12   ` kbuild test robot
2020-01-05  2:56   ` kbuild test robot
2020-01-11 19:58   ` kbuild test robot
2020-01-04 20:14 ` [PATCH v2 5/6] fs: expose internal interfaces open_detached_copy and do_reconfigure_mount James Bottomley
2020-01-04 20:14 ` [PATCH v2 6/6] fs: bind: add configfs type for bind mounts James Bottomley
2020-01-12 10:35   ` kbuild test robot
2020-01-12 10:35   ` [RFC PATCH] fs: bind: to_bind_data() can be static kbuild test robot
2020-01-05 16:23 ` [PATCH v2 0/6] introduce configfd as generalisation of fsconfig Christian Brauner
2020-01-05 17:51   ` James Bottomley
2020-01-05 18:02   ` James Bottomley
2020-01-08 17:07     ` Christian Brauner
2020-01-08 18:42       ` James Bottomley

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=20200106035830.6ok7ehpfcenns2hl@f53c9c00458a \
    --to=lkp@intel.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=christian@brauner.io \
    --cc=dhowells@redhat.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=viro@ZenIV.linux.org.uk \
    /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).