From: Carlos Maiolino <cem@kernel.org>
To: Srikanth C S <srikanth.c.s@oracle.com>
Cc: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
Darrick Wong <darrick.wong@oracle.com>,
Rajesh Sivaramasubramaniom
<rajesh.sivaramasubramaniom@oracle.com>,
Junxiao Bi <junxiao.bi@oracle.com>,
"david@fromorbit.com" <david@fromorbit.com>,
"Darrick J. Wong" <djwong@kernel.org>
Subject: Re: [External] : Re: [PATCH v3] fsck.xfs: mount/umount xfs fs to replay log before running xfs_repair
Date: Fri, 9 Dec 2022 10:51:46 +0100 [thread overview]
Message-ID: <20221209095146.72urohonkttuzkui@andromeda> (raw)
In-Reply-To: <MWHPR10MB1486C55C14A9D4F8CA32D33DA31B9@MWHPR10MB1486.namprd10.prod.outlook.com>
> > > So I am still wondering on how to proceed with this patch. Any
> > > comments would be helpful.
> >
> @Carlos Maiolino, Any comments or thoughts on this patch?
Sorry, didn't have time to look into it yet.
--
Carlos Maiolino
next prev parent reply other threads:[~2022-12-09 9:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <NdSU2Rq0FpWJ3II4JAnJNk-0HW5bns_UxhQ03sSOaek-nu9QPA-ZMx0HDXFtVx8ahgKhWe0Wcfh13NH0ZSwJjg==@protonmail.internalid>
2022-11-23 6:30 ` [PATCH v3] fsck.xfs: mount/umount xfs fs to replay log before running xfs_repair Srikanth C S
2022-11-23 8:36 ` Carlos Maiolino
[not found] ` <c-vuqhpmmrL6JSN0ZRnqX7c1BUcXw5gJ9L2UZ2lG3H8hCJRNIn_uan2rVHLDUPwgY24Nv3WZpiBt2nflhVadtA==@protonmail.internalid>
[not found] ` <CY4PR10MB1479D19A047EAB8558445EC7A30C9@CY4PR10MB1479.namprd10.prod.outlook.com>
2022-11-23 12:23 ` [External] : " Carlos Maiolino
2022-11-25 12:09 ` Srikanth C S
2022-11-28 23:04 ` Darrick J. Wong
2022-12-06 11:48 ` Srikanth C S
2022-12-09 9:51 ` Carlos Maiolino [this message]
2022-12-12 12:13 ` Carlos Maiolino
2022-12-13 9:39 ` Carlos Maiolino
2022-12-13 12:32 ` [External] : " Srikanth C S
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=20221209095146.72urohonkttuzkui@andromeda \
--to=cem@kernel.org \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=junxiao.bi@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=rajesh.sivaramasubramaniom@oracle.com \
--cc=srikanth.c.s@oracle.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