From: patchwork-bot+f2fs@kernel.org
To: Youling Tang <youling.tang@linux.dev>
Cc: viro@zeniv.linux.org.uk, brauner@kernel.org, jaegeuk@kernel.org,
chao@kernel.org, miklos@szeredi.hu, tangyouling@kylinos.cn,
jack@suse.cz, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH 1/3] fs: Export in_group_or_capable()
Date: Wed, 24 Jul 2024 02:16:46 +0000 [thread overview]
Message-ID: <172178740649.17759.11088131748657824514.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240620032335.147136-1-youling.tang@linux.dev>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Christian Brauner <brauner@kernel.org>:
On Thu, 20 Jun 2024 11:23:33 +0800 you wrote:
> From: Youling Tang <tangyouling@kylinos.cn>
>
> Export in_group_or_capable() as a VFS helper function.
>
> Signed-off-by: Youling Tang <tangyouling@kylinos.cn>
> ---
> fs/attr.c | 2 --
> fs/inode.c | 1 +
> include/linux/fs.h | 2 ++
> 3 files changed, 3 insertions(+), 2 deletions(-)
Here is the summary with links:
- [f2fs-dev,1/3] fs: Export in_group_or_capable()
https://git.kernel.org/jaegeuk/f2fs/c/9b6a14f08b48
- [f2fs-dev,2/3] f2fs: Use in_group_or_capable() helper
https://git.kernel.org/jaegeuk/f2fs/c/8444ee22adb0
- [f2fs-dev,3/3] fuse: Use in_group_or_capable() helper
https://git.kernel.org/jaegeuk/f2fs/c/153216cf7bd5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-07-24 2:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 3:23 [PATCH 1/3] fs: Export in_group_or_capable() Youling Tang
2024-06-20 3:23 ` [PATCH 2/3] f2fs: Use in_group_or_capable() helper Youling Tang
2024-06-20 3:23 ` [PATCH 3/3] fuse: " Youling Tang
2024-06-20 14:03 ` [PATCH 1/3] fs: Export in_group_or_capable() Christian Brauner
2024-07-24 2:16 ` patchwork-bot+f2fs [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=172178740649.17759.11088131748657824514.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=brauner@kernel.org \
--cc=chao@kernel.org \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=tangyouling@kylinos.cn \
--cc=viro@zeniv.linux.org.uk \
--cc=youling.tang@linux.dev \
/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