From: Jan Kara <jack@suse.cz>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Jan Kara <jack@suse.cz>, Amir Goldstein <amir73il@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fsnotify: Use NULL instead of 0 for pointer
Date: Wed, 30 Oct 2019 15:10:18 +0100 [thread overview]
Message-ID: <20191030141018.GP28525@quack2.suse.cz> (raw)
In-Reply-To: <dade5dda-6d1f-519d-e4e6-e29d2a44bed9@loongson.cn>
On Wed 30-10-19 21:12:37, Tiezhu Yang wrote:
> On 10/30/2019 08:21 PM, Jan Kara wrote:
> > On Tue 29-10-19 21:39:02, Tiezhu Yang wrote:
> > > Fix the following sparse warning:
> > >
> > > fs/notify/fdinfo.c:53:87: warning: Using plain integer as NULL pointer
> > >
> > > Fixes: be77196b809c ("fs, notify: add procfs fdinfo helper")
> > > Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
> > Thanks for the patch but similar patch already sits in my tree as commit
> > ddd06c36bdb "fsnotify/fdinfo: exportfs_encode_inode_fh() takes pointer as
> > 4th argument". I'll send it to Linus in the next merge window.
> >
> > Honza
>
> Thanks for your reply. I can not find your tree about fs/notify
> in the MAINTAINERS file, so this patch is based on Linus's tree.
> Sorry for the noise, you can ignore it.
>
> By the way, could you add your tree in the MAINTAINERS file?
Good idea! Added. Thanks!
Honza
> > > ---
> > > fs/notify/fdinfo.c | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/fs/notify/fdinfo.c b/fs/notify/fdinfo.c
> > > index 1e2bfd2..cd2846e 100644
> > > --- a/fs/notify/fdinfo.c
> > > +++ b/fs/notify/fdinfo.c
> > > @@ -50,7 +50,8 @@ static void show_mark_fhandle(struct seq_file *m, struct inode *inode)
> > > f.handle.handle_bytes = sizeof(f.pad);
> > > size = f.handle.handle_bytes >> 2;
> > > - ret = exportfs_encode_inode_fh(inode, (struct fid *)f.handle.f_handle, &size, 0);
> > > + ret = exportfs_encode_inode_fh(inode, (struct fid *)f.handle.f_handle,
> > > + &size, NULL);
> > > if ((ret == FILEID_INVALID) || (ret < 0)) {
> > > WARN_ONCE(1, "Can't encode file handler for inotify: %d\n", ret);
> > > return;
> > > --
> > > 2.1.0
> > >
> > >
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2019-10-30 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 13:39 [PATCH] fsnotify: Use NULL instead of 0 for pointer Tiezhu Yang
2019-10-30 12:21 ` Jan Kara
2019-10-30 13:12 ` Tiezhu Yang
2019-10-30 14:10 ` Jan Kara [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=20191030141018.GP28525@quack2.suse.cz \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yangtiezhu@loongson.cn \
/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