From: Andrey Albershteyn <aalbersh@redhat.com>
To: linux-xfs@vger.kernel.org, aalbersh@kernel.org, cem@kernel.org,
cmaiolino@redhat.com, djwong@kernel.org, hch@lst.de,
pchelkin@ispras.ru, pranav.tyagi03@gmail.com,
sandeen@redhat.com
Subject: [PATCH v2 0/12] xfsprogs: libxfs sync v6.17
Date: Thu, 9 Oct 2025 14:08:24 +0200 [thread overview]
Message-ID: <cover.1760011614.patch-series@thinky> (raw)
Hey all,
This is libxfs sync with v6.17.
---
0 files changed, 0 insertions(+), 0 deletions(-)
--
- Andrey
next reply other threads:[~2025-10-09 12:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 12:08 Andrey Albershteyn [this message]
2025-10-09 12:08 ` [PATCH v2 1/11] xfs: rename diff_two_keys routines Fedor Pchelkin
2025-10-09 12:08 ` [PATCH v2 2/11] xfs: rename key_diff routines Fedor Pchelkin
2025-10-09 12:09 ` [PATCH v2 3/11] xfs: refactor cmp_two_keys routines to take advantage of cmp_int() Fedor Pchelkin
2025-10-09 12:09 ` [PATCH v2 4/11] xfs: refactor cmp_key_with_cur " Fedor Pchelkin
2025-10-09 12:09 ` [PATCH v2 5/11] xfs: use a proper variable name and type for storing a comparison result Fedor Pchelkin
2025-10-09 12:09 ` [PATCH v2 6/11] xfs: refactor xfs_btree_diff_two_ptrs() to take advantage of cmp_int() Fedor Pchelkin
2025-10-09 12:09 ` [PATCH v2 7/11] xfs: return the allocated transaction from xfs_trans_alloc_empty Christoph Hellwig
2025-10-09 12:09 ` [PATCH v2 8/11] xfs: improve the xg_active_ref check in xfs_group_free Christoph Hellwig
2025-10-09 12:10 ` [PATCH v2 9/11] fs/xfs: replace strncpy with memtostr_pad() Pranav Tyagi
2025-10-09 12:10 ` [PATCH v2 10/11] xfs: don't use a xfs_log_iovec for ri_buf in log recovery Christoph Hellwig
2025-10-09 12:10 ` [PATCH v2 11/11] xfs: do not propagate ENODATA disk errors into xattr code Eric Sandeen
2025-10-09 14:57 ` [PATCH v2 0/12] xfsprogs: libxfs sync v6.17 Darrick J. Wong
2025-10-10 5:08 ` Christoph Hellwig
2025-10-10 9:17 ` Andrey Albershteyn
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=cover.1760011614.patch-series@thinky \
--to=aalbersh@redhat.com \
--cc=aalbersh@kernel.org \
--cc=cem@kernel.org \
--cc=cmaiolino@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
--cc=pchelkin@ispras.ru \
--cc=pranav.tyagi03@gmail.com \
--cc=sandeen@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.