From: Chandan Babu R <chandanbabu@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: chandan.babu@gmail.com, david@fromorbit.com, dchinner@redhat.com,
linux-xfs@vger.kernel.org, peterz@infradead.org,
ritesh.list@gmail.com, sandeen@sandeen.net, tglx@linutronix.de
Subject: Re: [GIT PULL] xfs: fix ro mounting with unknown rocompat features
Date: Wed, 20 Sep 2023 15:50:04 +0530 [thread overview]
Message-ID: <87jzsl6sri.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <169513911841.1384408.4221257193552110896.stg-ugh@frogsfrogsfrogs>
On Tue, Sep 19, 2023 at 09:01:42 AM -0700, Darrick J. Wong wrote:
> Hi Chandan,
>
> Please pull this branch with changes for xfs for 6.6-rc2.
>
> As usual, I did a test-merge with the main upstream branch as of a few
> minutes ago, and didn't see any conflicts. Please let me know if you
> encounter any problems.
>
Darrick, Unfortunately applying fix-efi-recovery-6.6_2023-09-12 tag pulls in
the older version of "xfs: fix log recovery when unknown rocompat bits are
set".
I think it is best to continue having the older version of "xfs: fix log
recovery when unknown rocompat bits are set" patch i.e. I will include the
current version of xfs-6.6-fixes-1 tag in my pull request to Linus instead of
replacing commits from fix-ro-mounts-6.6_2023-09-12 with
fix-ro-mounts-6.6_2023-09-19.
Sorry about the noise.
--
Chandan
next prev parent reply other threads:[~2023-09-20 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 16:01 [GIT PULL] xfs: fix ro mounting with unknown rocompat features Darrick J. Wong
2023-09-20 10:20 ` Chandan Babu R [this message]
2023-09-20 14:24 ` Darrick J. Wong
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=87jzsl6sri.fsf@debian-BULLSEYE-live-builder-AMD64 \
--to=chandanbabu@kernel.org \
--cc=chandan.babu@gmail.com \
--cc=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=ritesh.list@gmail.com \
--cc=sandeen@sandeen.net \
--cc=tglx@linutronix.de \
/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