From: gregkh@linuxfoundation.org (Greg KH)
Subject: [PATCH] staging: erofs: remove needless dummy functions of erofs_{get,list}xattr
Date: Fri, 21 Jun 2019 09:02:44 +0200 [thread overview]
Message-ID: <20190621070244.GC3029@kroah.com> (raw)
In-Reply-To: <f6b2ced7-79ea-9cc6-5e88-43552b5947a9@huawei.com>
On Fri, Jun 21, 2019@01:08:39PM +0800, Gao Xiang wrote:
> Hi Yue,
>
> On 2019/6/21 12:08, Yue Hu wrote:
> > From: Yue Hu <huyue2 at yulong.com>
> >
> > The two dummy functions of erofs_getxattr()/erofs_listxattr() will never
> > be used if disable CONFIG_EROFS_FS_XATTR.
> >
> > Signed-off-by: Yue Hu <huyue2 at yulong.com>
> > ---
> > drivers/staging/erofs/xattr.h | 13 -------------
> > 1 file changed, 13 deletions(-)
> >
> > diff --git a/drivers/staging/erofs/xattr.h b/drivers/staging/erofs/xattr.h
> > index 35ba5ac..2c1e46f 100644
> > --- a/drivers/staging/erofs/xattr.h
> > +++ b/drivers/staging/erofs/xattr.h
> > @@ -72,19 +72,6 @@ static inline const struct xattr_handler *erofs_xattr_handler(unsigned index)
> >
> > int erofs_getxattr(struct inode *, int, const char *, void *, size_t);
> > ssize_t erofs_listxattr(struct dentry *, char *, size_t);
> > -#else
> > -static int __maybe_unused erofs_getxattr(struct inode *inode, int index,
> > - const char *name,
> > - void *buffer, size_t buffer_size)
> > -{
> > - return -ENOTSUPP;
> > -}
> > -
> > -static ssize_t __maybe_unused erofs_listxattr(struct dentry *dentry,
> > - char *buffer, size_t buffer_size)
> > -{
> > - return -ENOTSUPP;
> > -}
> > #endif
>
> It's mainly used for erofs to directly call erofs_getxattr / erofs_listxattr (even
> xattr feature is off) to get a xattr in erofs itself, just follow what other
> filesystems (e.g. f2fs) did, although these apis have not been used internally
> yet but used as callbacks in inode_operations only.
>
> I have no positive or negative tendency since the patch is minor and the only
> benefit of this patch is that it removes some code which seems redundant currently.
> However, if erofs_getxattr is needed later, it should be added back of course.
> Therefore I think it could depend on Greg whether accept this patch or not.
Let's leave this as-is for now.
thanks,
greg k-h
prev parent reply other threads:[~2019-06-21 7:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 4:08 [PATCH] staging: erofs: remove needless dummy functions of erofs_{get, list}xattr Yue Hu
2019-06-21 5:08 ` [PATCH] staging: erofs: remove needless dummy functions of erofs_{get,list}xattr Gao Xiang
2019-06-21 7:02 ` Greg KH [this message]
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=20190621070244.GC3029@kroah.com \
--to=gregkh@linuxfoundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.