From: Eryu Guan <guaneryu@gmail.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH] misc: xfs_fsop_geom_t -> struct xfs_fsop_geom
Date: Thu, 25 Apr 2019 15:30:27 +0800 [thread overview]
Message-ID: <20190425073027.GA15846@desktop> (raw)
In-Reply-To: <20190422154820.GA4675@magnolia>
On Mon, Apr 22, 2019 at 08:48:20AM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> Remove the typedef usage for the xfs geometry structure.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
I guess this is due to patch "xfs: bump XFS_IOC_FSGEOMETRY to v5
structures" which removes the xfs_fsop_geom_t typedef? And I'm wondering
if xfs/122 needs update too? as xfs/122.out contains an xfs_fsop_geom_t
entry as well.
Thanks,
Eryu
> ---
> dmapi/src/suite1/cmd/make_rt_sparse.c | 2 +-
> ltp/fsstress.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/dmapi/src/suite1/cmd/make_rt_sparse.c b/dmapi/src/suite1/cmd/make_rt_sparse.c
> index 14ee8a0d..13fd3676 100644
> --- a/dmapi/src/suite1/cmd/make_rt_sparse.c
> +++ b/dmapi/src/suite1/cmd/make_rt_sparse.c
> @@ -36,7 +36,7 @@ main(
> int argc,
> char **argv)
> {
> - xfs_fsop_geom_t geom;
> + struct xfs_fsop_geom geom;
> struct fsxattr fsx;
> struct dioattr dio;
> char *pathname;
> diff --git a/ltp/fsstress.c b/ltp/fsstress.c
> index 450cf4f1..279da9f1 100644
> --- a/ltp/fsstress.c
> +++ b/ltp/fsstress.c
> @@ -294,7 +294,7 @@ int errrange;
> int errtag;
> opty_t *freq_table;
> int freq_table_size;
> -xfs_fsop_geom_t geom;
> +struct xfs_fsop_geom geom;
> char *homedir;
> int *ilist;
> int ilistlen;
next prev parent reply other threads:[~2019-04-25 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 15:48 [PATCH] misc: xfs_fsop_geom_t -> struct xfs_fsop_geom Darrick J. Wong
2019-04-25 7:30 ` Eryu Guan [this message]
2019-04-25 15:50 ` Darrick J. Wong
2019-04-26 2:30 ` Eryu Guan
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=20190425073027.GA15846@desktop \
--to=guaneryu@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=fstests@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.