From: Christian Brauner <brauner@kernel.org>
To: Abhinav Singh <singhabhinav9051571833@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
nvdimm@lists.linux.dev,
linux-kernel-mentees@lists.linuxfoundation.org,
viro@zeniv.linux.org.uk, dan.j.williams@intel.com,
willy@infradead.org, jack@suse.cz
Subject: Re: [PATCH] fs : Fix warning using plain integer as NULL
Date: Wed, 8 Nov 2023 11:01:29 +0100 [thread overview]
Message-ID: <20231108-rasur-zugute-1f2c148eae10@brauner> (raw)
In-Reply-To: <20231108044550.1006555-1-singhabhinav9051571833@gmail.com>
On Wed, 08 Nov 2023 10:15:50 +0530, Abhinav Singh wrote:
> Sparse static analysis tools generate a warning with this message
> "Using plain integer as NULL pointer". In this case this warning is
> being shown because we are trying to initialize pointer to NULL using
> integer value 0.
>
>
Applied to the vfs.misc branch of the vfs/vfs.git tree.
Patches in the vfs.misc branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.misc
[1/1] fs : Fix warning using plain integer as NULL
https://git.kernel.org/vfs/vfs/c/372bfbd2ea43
next prev parent reply other threads:[~2023-11-08 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 4:45 Abhinav Singh
2023-11-08 10:01 ` Christian Brauner [this message]
2023-11-08 10:15 ` Jan Kara
2023-11-08 10:47 ` Abhinav Singh
2023-11-08 10:50 ` Abhinav Singh
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=20231108-rasur-zugute-1f2c148eae10@brauner \
--to=brauner@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=singhabhinav9051571833@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®