From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
cem@kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] libfrog: Unconditionally build fsprops.c
Date: Mon, 19 Aug 2024 08:23:41 -0700 [thread overview]
Message-ID: <ZsNjfXWaLc8w1r1S@infradead.org> (raw)
In-Reply-To: <20240819151216.GP865349@frogsfrogsfrogs>
On Mon, Aug 19, 2024 at 08:12:16AM -0700, Darrick J. Wong wrote:
>
> How about we just opencode ATTR_ENTRY in libfrog and then we can get rid
> of the libattr dependency for it and xfs_scrub? IIRC that's the only
> piece of libattr that those pieces actually need.
We'd also have to switch from attrlist_ent to xfs_attrlist_ent
and maybe a few similar substitutions, but otherwise it should work.
While we're at it, it might be worth to do the same for scrub and
get rid of the libattr dependency entirely.
next prev parent reply other threads:[~2024-08-19 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 13:22 [PATCH] libfrog: Unconditionally build fsprops.c cem
2024-08-19 14:09 ` Christoph Hellwig
2024-08-19 15:12 ` Darrick J. Wong
2024-08-19 15:23 ` Christoph Hellwig [this message]
2024-08-19 15:57 ` Carlos Maiolino
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=ZsNjfXWaLc8w1r1S@infradead.org \
--to=hch@infradead.org \
--cc=cem@kernel.org \
--cc=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