From: "Darrick J. Wong" <djwong@kernel.org>
To: xfs <linux-xfs@vger.kernel.org>
Subject: no xfs-5.13-fixes branch yet
Date: Thu, 13 May 2021 18:21:25 -0700 [thread overview]
Message-ID: <20210514012125.GI9675@magnolia> (raw)
Hi everyone,
Just FYI, I decided not to move forward with a -fixes branch based on
5.13-rc1 because of the data corruptions reported with bfq[1] and
dm-crypt[2]. Hopefully at least the first one will get fixed in rc2 and
I'll base it off that. I didn't feel like torching peoples' testing VMs
like last cycle.
Also I might be out Tuesday and Wednesday of next week.
--D
[1] https://lore.kernel.org/linux-block/20210512094352.85545-1-paolo.valente@linaro.org/
[2] https://lore.kernel.org/linux-ext4/20210513094222.17635-1-nanich.lee@samsung.com/
reply other threads:[~2021-05-14 1:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210514012125.GI9675@magnolia \
--to=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