From: Christian Brauner <brauner@kernel.org>
To: Min-Hua Chen <minhuadotchen@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-unionfs@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: [PATCH] fs: fix incorrect fmode_t casts
Date: Mon, 15 May 2023 13:17:58 +0200 [thread overview]
Message-ID: <20230515-hirsch-robust-fb5b936fb943@brauner> (raw)
In-Reply-To: <20230502232210.119063-1-minhuadotchen@gmail.com>
On Wed, 03 May 2023 07:22:08 +0800, Min-Hua Chen wrote:
> Use __FMODE_NONOTIFY instead of FMODE_NONOTIFY to fixes
> the following sparce warnings:
> fs/overlayfs/file.c:48:37: sparse: warning: restricted fmode_t degrades to integer
> fs/overlayfs/file.c:128:13: sparse: warning: restricted fmode_t degrades to integer
> fs/open.c:1159:21: sparse: warning: restricted fmode_t degrades to integer
>
>
> [...]
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.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.misc
[1/1] fs: fix incorrect fmode_t casts
https://git.kernel.org/vfs/vfs/c/079ad16ded46
prev parent reply other threads:[~2023-05-15 11:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 23:22 [PATCH] fs: fix incorrect fmode_t casts Min-Hua Chen
2023-05-15 11:17 ` Christian Brauner [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=20230515-hirsch-robust-fb5b936fb943@brauner \
--to=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=minhuadotchen@gmail.com \
--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).