From: Christoph Hellwig <hch@lst.de>
To: Dave Chinner <david@fromorbit.com>
Cc: Carlos Maiolino <cem@kernel.org>,
Andrey Albershteyn <aalbersh@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>,
Chandan Babu R <chandanbabu@kernel.org>,
Eric Sandeen <sandeen@redhat.com>,
linux-xfs@vger.kernel.org
Subject: Good name for xfs.h/libxfs_priv.h in libxfs
Date: Wed, 10 Dec 2025 07:08:48 +0100 [thread overview]
Message-ID: <20251210060848.GA31741@lst.de> (raw)
In-Reply-To: <aTFOsmgaPOhtaDeL@dread.disaster.area>
Trying to bring this up again. I want a common name for
xfs.h/libxfs_priv.h so that sharing libxfs code is easier.
My initial proposal was xfs_priv.h, which Dave didn't like for a valid
reason. His counter proposal was to just use xfs_linux.h, which is
fine with me. Another option would be xfs_plaform.h to be more system
independent. Both are fine with me, as is any other reasonable option.
I've added our regulars to ask if there are any strong preferences
or dislikes for any of the names, or a suggestion for an even better
one.
next prev parent reply other threads:[~2025-12-10 6:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 13:37 [PATCH, RFC] rename xfs.h Christoph Hellwig
2025-12-02 13:37 ` [PATCH] xfs: rename xfs.h to xfs_priv.h Christoph Hellwig
2025-12-04 9:04 ` [PATCH, RFC] rename xfs.h Dave Chinner
2025-12-04 9:23 ` Christoph Hellwig
2025-12-04 17:21 ` Darrick J. Wong
2025-12-05 8:12 ` Christoph Hellwig
2025-12-05 16:29 ` Darrick J. Wong
2025-12-08 4:30 ` Dave Chinner
2025-12-10 6:08 ` Christoph Hellwig [this message]
2025-12-10 6:23 ` Good name for xfs.h/libxfs_priv.h in libxfs Darrick J. Wong
2025-12-10 22:51 ` Eric Sandeen
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=20251210060848.GA31741@lst.de \
--to=hch@lst.de \
--cc=aalbersh@kernel.org \
--cc=cem@kernel.org \
--cc=chandanbabu@kernel.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox