From: Eric Sandeen <sandeen@redhat.com>
To: Gao Xiang <hsiangkao@redhat.com>,
"Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Gao Xiang <hsiangkao@aol.com>,
linux-xfs <linux-xfs@vger.kernel.org>,
Dave Chinner <david@fromorbit.com>
Subject: Re: [PATCH v4 3/3] xfsprogs: make use of xfs_validate_stripe_factors()
Date: Fri, 9 Oct 2020 08:02:02 -0500 [thread overview]
Message-ID: <b00455fd-a017-8daf-2b15-d3062f0d6bef@redhat.com> (raw)
In-Reply-To: <20201009005847.GB10631@xiangao.remote.csb>
On 10/8/20 7:58 PM, Gao Xiang wrote:
>> Unless we get rid of the weird libxfs macro thing, you're supposed to
>> use prefixes in userspace.
> I vaguely remembered Christoph sent out a patch intending to get
> rid of xfsprogs libxfs_ prefix months ago, so I assumed there was
> no need to introduce any new libxfs_ userspace API wrappers anymore.
He did, and it's on my (perpetual) TODO list to get that finally reviewed,
sorry.
For now we still have libxfs*
-Eric
> But yeah, will add such libxfs_ marco wrapper in the next version.
>
> Thanks,
> Gao Xiang
>
next prev parent reply other threads:[~2020-10-09 13:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201007140402.14295-1-hsiangkao.ref@aol.com>
2020-10-07 14:03 ` [PATCH v4 0/3] xfsprogs: consolidate stripe validation Gao Xiang
2020-10-07 14:04 ` [PATCH v4 1/3] xfsprogs: allow i18n to xfs printk Gao Xiang
2020-10-07 15:28 ` Darrick J. Wong
2020-10-09 1:01 ` Gao Xiang
2020-10-07 14:04 ` [PATCH v4 2/3] xfs: introduce xfs_validate_stripe_factors() Gao Xiang
2020-10-07 22:29 ` Darrick J. Wong
2020-10-09 0:54 ` Gao Xiang
2020-10-07 14:04 ` [PATCH v4 3/3] xfsprogs: make use of xfs_validate_stripe_factors() Gao Xiang
2020-10-07 22:30 ` Darrick J. Wong
2020-10-09 0:58 ` Gao Xiang
2020-10-09 13:02 ` Eric Sandeen [this message]
2020-10-09 13:50 ` Gao Xiang
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=b00455fd-a017-8daf-2b15-d3062f0d6bef@redhat.com \
--to=sandeen@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=hsiangkao@aol.com \
--cc=hsiangkao@redhat.com \
--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 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.