From: Carlos Maiolino <cem@kernel.org>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfsprogs: for-next updated to 364cc9546
Date: Mon, 24 Apr 2023 12:48:50 +0200 [thread overview]
Message-ID: <20230424104850.ctqyp2crom3du2tm@andromeda> (raw)
Hello.
The xfsprogs for-next branch, located at:
https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/refs/?h=for-next
Has just been updated.
Patches often get missed, so if your outstanding patches are properly reviewed on
the list and not included in this update, please let me know.
The new head of the for-next branch is commit:
364cc95468f737725b90a91bf11b8e0452aa0122
3 new commits:
Darrick J. Wong (2):
[d8a19f298] libfrog: move crc32c selftest buffer into a separate file
[b9d29568e] misc: test the dir/attr hash before formatting or repairing fs
Eric Sandeen (1):
[364cc9546] xfsprogs: nrext64 option should be in [inode] section of mkfs conf files
Code Diffstat:
libfrog/Makefile | 7 +-
libfrog/crc32cselftest.h | 533 +----------------------------------------------
libfrog/dahashselftest.h | 172 +++++++++++++++
libfrog/randbytes.c | 527 ++++++++++++++++++++++++++++++++++++++++++++++
libfrog/randbytes.h | 11 +
mkfs/lts_4.19.conf | 2 +-
mkfs/lts_5.10.conf | 2 +-
mkfs/lts_5.15.conf | 2 +-
mkfs/lts_5.4.conf | 2 +-
mkfs/lts_6.1.conf | 2 +-
mkfs/xfs_mkfs.c | 8 +
repair/init.c | 5 +
12 files changed, 743 insertions(+), 530 deletions(-)
create mode 100644 libfrog/dahashselftest.h
create mode 100644 libfrog/randbytes.c
create mode 100644 libfrog/randbytes.h
--
Carlos Maiolino
reply other threads:[~2023-04-24 10:48 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=20230424104850.ctqyp2crom3du2tm@andromeda \
--to=cem@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