From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
cem@kernel.org, linux-xfs@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] xfs: fix !quota build
Date: Wed, 11 Dec 2024 18:36:01 +0100 [thread overview]
Message-ID: <20241211173601.GA19633@lst.de> (raw)
In-Reply-To: <20241211173318.GB6698@frogsfrogsfrogs>
On Wed, Dec 11, 2024 at 09:33:18AM -0800, Darrick J. Wong wrote:
> Also, can we get rid of CONFIG_XFS_{QUOTA,POSIX_ACL}? Maintaining all
> these dummy macros is ... irritating.
I have a slightly older branch that looked into the config options
including module size comparisms. Quota is surprisingly big, RT less so,
but ACL should be a no-brainer:
http://git.infradead.org/?p=users/hch/xfs.git;a=shortlog;h=refs/heads/xfs-config-options
prev parent reply other threads:[~2024-12-11 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 3:54 [PATCH] xfs: fix !quota build Christoph Hellwig
2024-12-11 9:42 ` Carlos Maiolino
2024-12-11 17:33 ` Darrick J. Wong
2024-12-11 17:36 ` Christoph Hellwig [this message]
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=20241211173601.GA19633@lst.de \
--to=hch@lst.de \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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