From: Pavel Reichl <preichl@redhat.com>
To: "Darrick J. Wong" <djwong@kernel.org>, cem@kernel.org
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/2] xfs_repair: always perform extended xattr checks on uncertain inodes
Date: Mon, 5 Jun 2023 19:17:56 +0200 [thread overview]
Message-ID: <098a2385-a012-bada-1cbf-db9401def3da@redhat.com> (raw)
In-Reply-To: <168597945009.1226372.4924137788610504146.stgit@frogsfrogsfrogs>
LGTM & Builds
Reviewed-by: Pavel Reichl <preichl@redhat.com>
next prev parent reply other threads:[~2023-06-05 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ylt88sC7wPqlsEe-9kVGAOzvu9xJonNujqD2n1YCftGJgq3r3dGy0wswBrjsSKtsPcypJo5q9wncj9pGilR8BQ==@protonmail.internalid>
2023-06-05 15:37 ` [PATCHSET 0/2] xfs_repair: fix missing corruption detection Darrick J. Wong
2023-06-05 15:37 ` [PATCH 1/2] xfs_repair: don't add junked entries to the rebuilt directory Darrick J. Wong
2023-06-05 17:13 ` Pavel Reichl
2023-06-05 15:37 ` [PATCH 2/2] xfs_repair: always perform extended xattr checks on uncertain inodes Darrick J. Wong
2023-06-05 17:17 ` Pavel Reichl [this message]
2023-06-06 9:16 ` [PATCHSET 0/2] xfs_repair: fix missing corruption detection Carlos Maiolino
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=098a2385-a012-bada-1cbf-db9401def3da@redhat.com \
--to=preichl@redhat.com \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-xfs@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