From: "Darrick J. Wong" <djwong@kernel.org>
To: Andrey Albershteyn <aalbersh@redhat.com>
Cc: xfs <linux-xfs@vger.kernel.org>, Christoph Hellwig <hch@infradead.org>
Subject: [PATCHBOMB v4] xfsprogs: (more) everything I have for 6.12
Date: Wed, 20 Nov 2024 16:07:05 -0800 [thread overview]
Message-ID: <20241121000705.GE9438@frogsfrogsfrogs> (raw)
Hi Andrey,
My newest xfs_repair fixes for xfsprogs 6.12 have completed review, and
there was a late libxfs change that Carlos merged. I'm about to send
you pull requests for all of those branches. However, I'm first
resending all those patches to the list so that they are archived in
their final form.
With these patches pulled, I'm done with 6.12. On to 6.13!
(You might have already pulled these three patches, in which case
disregard them and the pull requests.)
--D
next reply other threads:[~2024-11-21 0:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 0:07 Darrick J. Wong [this message]
2024-11-21 0:08 ` [PATCHSET 1/2] libxfs: new code for 6.12 Darrick J. Wong
2024-11-21 0:09 ` [PATCH 1/1] xfs: Reduce unnecessary searches when searching for the best extents Darrick J. Wong
2024-11-21 0:08 ` [PATCHSET 2/2] xfs: bug fixes for 6.12 Darrick J. Wong
2024-11-21 0:09 ` [PATCH 1/2] xfs_repair: fix crasher in pf_queuing_worker Darrick J. Wong
2024-11-21 0:09 ` [PATCH 2/2] xfs_repair: synthesize incore inode tree records when required 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=20241121000705.GE9438@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=aalbersh@redhat.com \
--cc=hch@infradead.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