From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to create selinux label during whiteout initialization
Date: Wed, 21 Feb 2024 18:10:31 +0000 [thread overview]
Message-ID: <170853903112.7043.10216556441891626581.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240207070548.3095087-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 7 Feb 2024 15:05:48 +0800 you wrote:
> generic/700 - output mismatch (see /media/fstests/results//generic/700.out.bad)
> --- tests/generic/700.out 2023-03-28 10:40:42.735529223 +0000
> +++ /media/fstests/results//generic/700.out.bad 2024-02-06 04:37:56.000000000 +0000
> @@ -1,2 +1,4 @@
> QA output created by 700
> +/mnt/scratch_f2fs/f1: security.selinux: No such attribute
> +/mnt/scratch_f2fs/f2: security.selinux: No such attribute
> Silence is golden
> ...
> (Run 'diff -u /media/fstests/tests/generic/700.out /media/fstests/results//generic/700.out.bad' to see the entire diff)
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to create selinux label during whiteout initialization
https://git.kernel.org/jaegeuk/f2fs/c/697c9124d70a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2024-02-21 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 7:05 [f2fs-dev] [PATCH] f2fs: fix to create selinux label during whiteout initialization Chao Yu
2024-02-21 18:10 ` 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=170853903112.7043.10216556441891626581.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).