From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: aalbersh@kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCHSET 2/2] xfsprogs: various bug fixes for 6.19
Date: Fri, 20 Feb 2026 08:44:00 -0800 [thread overview]
Message-ID: <20260220164400.GZ6490@frogsfrogsfrogs> (raw)
In-Reply-To: <20260220162755.GX6490@frogsfrogsfrogs>
On Fri, Feb 20, 2026 at 08:27:55AM -0800, Darrick J. Wong wrote:
> On Fri, Feb 20, 2026 at 07:35:33AM -0800, Christoph Hellwig wrote:
> > This all (or at least mostly?) seems to be in xfsprogs for-next already.
>
> Oh, I must've missed the announcement. And then I also missed that
> gitweb shifted because that stupid Anubis thing usually won't load due
> to its 300K of web artifacts also 503'ing due to excess load.
>
> Will rebase and resend whatever's necessary. Sorry about the noise.
Indeed this whole patchset is already merged, everyone please disregard
it.
--D
prev parent reply other threads:[~2026-02-20 16:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 23:43 [PATCHSET 2/2] xfsprogs: various bug fixes for 6.19 Darrick J. Wong
2026-02-19 23:46 ` [PATCH 1/6] mkfs: set rtstart from user-specified dblocks Darrick J. Wong
2026-02-19 23:47 ` [PATCH 2/6] xfs_logprint: print log data to the screen in host-endian order Darrick J. Wong
2026-02-19 23:47 ` [PATCH 3/6] mkfs: quiet down warning about insufficient write zones Darrick J. Wong
2026-02-19 23:47 ` [PATCH 4/6] xfs_mdrestore: fix restoration on filesystems with 4k sectors Darrick J. Wong
2026-02-19 23:47 ` [PATCH 5/6] debian: don't explicitly reload systemd from postinst Darrick J. Wong
2026-02-19 23:48 ` [PATCH 6/6] xfs_scrub_all: fix non-service-mode arguments to xfs_scrub Darrick J. Wong
2026-02-20 15:35 ` [PATCHSET 2/2] xfsprogs: various bug fixes for 6.19 Christoph Hellwig
2026-02-20 16:27 ` Darrick J. Wong
2026-02-20 16:44 ` Darrick J. Wong [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=20260220164400.GZ6490@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=aalbersh@kernel.org \
--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