From: cem@kernel.org
To: linux-xfs@vger.kernel.org
Cc: djwong@kernel.org, hch@lst.de, hch@infradead.org
Subject: [PATCH 0/3] Get rid of libattr dependency
Date: Tue, 27 Aug 2024 13:50:21 +0200 [thread overview]
Message-ID: <20240827115032.406321-1-cem@kernel.org> (raw)
From: Carlos Maiolino <cem@kernel.org>
libxfs already defines most of the structs used by xfsprogs, so we don't
really need to link against libattr.
To make things more organized, and smaller easy to review patches, remove it in steps,
This is only compile-tested so far. I just sent the patches for testing,
but giving it might take a while, I'm sending it to the list for review.
Carlos Maiolino (3):
libhandle: Remove libattr dependency
libfrog: remove libattr dependency
scrub: Remove libattr dependency
include/handle.h | 3 +--
include/jdm.h | 5 ++---
libfrog/Makefile | 7 ++-----
libfrog/attr.h | 23 +++++++++++++++++++++++
libfrog/fsprops.c | 13 ++++++-------
libhandle/handle.c | 2 +-
libhandle/jdm.c | 14 +++++++-------
scrub/Makefile | 4 ----
scrub/phase5.c | 11 ++++-------
9 files changed, 46 insertions(+), 36 deletions(-)
create mode 100644 libfrog/attr.h
Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
--
2.46.0
next reply other threads:[~2024-08-27 11:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 11:50 cem [this message]
2024-08-27 11:50 ` [PATCH 1/3] libhandle: Remove libattr dependency cem
2024-08-27 12:12 ` Christoph Hellwig
2024-08-27 14:44 ` Darrick J. Wong
2024-08-28 4:33 ` Christoph Hellwig
2024-08-27 14:41 ` Darrick J. Wong
2024-08-28 4:34 ` Christoph Hellwig
2024-08-29 13:18 ` Carlos Maiolino
2024-08-27 11:50 ` [PATCH 2/3] libfrog: remove " cem
2024-08-27 12:15 ` Christoph Hellwig
2024-08-27 12:24 ` Carlos Maiolino
2024-08-27 11:50 ` [PATCH 3/3] scrub: Remove " cem
2024-08-27 12:16 ` Christoph Hellwig
2024-08-27 12:27 ` Carlos Maiolino
2024-08-27 14:36 ` Darrick J. Wong
2024-08-28 4:35 ` Christoph Hellwig
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=20240827115032.406321-1-cem@kernel.org \
--to=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--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