From: Christian Brauner <brauner@kernel.org>
To: Shuah Khan <shuah@kernel.org>, Miklos Szeredi <miklos@szeredi.hu>,
Chen Linxuan <chenlinxuan@uniontech.com>
Cc: Christian Brauner <brauner@kernel.org>,
zhanjun@uniontech.com, niecheng1@uniontech.com,
Shuah Khan <skhan@linuxfoundation.org>,
Amir Goldstein <amir73il@gmail.com>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v4] selftests: filesystems: Add functional test for the abort file in fusectl
Date: Thu, 19 Jun 2025 12:04:15 +0200 [thread overview]
Message-ID: <20250619-nennen-eisvogel-6311408892e0@brauner> (raw)
In-Reply-To: <20250612094033.2538122-2-chenlinxuan@uniontech.com>
On Thu, 12 Jun 2025 17:40:29 +0800, Chen Linxuan wrote:
> This patch add a simple functional test for the "abort" file
> in fusectlfs (/sys/fs/fuse/connections/ID/about).
>
> A simple fuse daemon is added for testing.
>
> Related discussion can be found in the link below.
>
> [...]
Applied to the vfs-6.17.selftests branch of the vfs/vfs.git tree.
Patches in the vfs-6.17.selftests 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-6.17.selftests
[1/1] selftests: filesystems: Add functional test for the abort file in fusectl
https://git.kernel.org/vfs/vfs/c/0f505cf71c63
next prev parent reply other threads:[~2025-06-19 10:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 9:40 Chen Linxuan
2025-06-18 20:52 ` Shuah Khan
2025-06-19 10:03 ` Christian Brauner
2025-06-19 10:04 ` Christian Brauner [this message]
2025-07-17 7:13 ` Amir Goldstein
2025-08-05 19:12 ` Miklos Szeredi
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=20250619-nennen-eisvogel-6311408892e0@brauner \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=chenlinxuan@uniontech.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=niecheng1@uniontech.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=zhanjun@uniontech.com \
/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®