From: Eryu Guan <guan@eryu.me>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: guaneryu@gmail.com, linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH 0/4] xfstests: fix compiler warnings with fsx/fsstress
Date: Sun, 15 Nov 2020 17:12:53 +0800 [thread overview]
Message-ID: <20201115091253.GJ3853@desktop> (raw)
In-Reply-To: <160505547722.1389938.14377167906399924976.stgit@magnolia>
On Tue, Nov 10, 2020 at 04:44:37PM -0800, Darrick J. Wong wrote:
> Hi all,
>
> Fix all the compiler warnings emitted when building fsstress and fsx.
I've taken the first 3 patches, and left the last one for now :)
Thanks,
Eryu
>
> If you're going to start using this mess, you probably ought to just
> pull from my git trees, which are linked below.
>
> This is an extraordinary way to destroy everything. Enjoy!
> Comments and questions are, as always, welcome.
>
> --D
>
> fstests git tree:
> https://git.kernel.org/cgit/linux/kernel/git/djwong/xfstests-dev.git/log/?h=fix-fsx-and-fsstress-warnings
> ---
> ltp/fsstress.c | 102 ++++++++++++++++++++++++++------------------------------
> ltp/fsx.c | 5 +--
> 2 files changed, 50 insertions(+), 57 deletions(-)
prev parent reply other threads:[~2020-11-15 9:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 0:44 [PATCH 0/4] xfstests: fix compiler warnings with fsx/fsstress Darrick J. Wong
2020-11-11 0:44 ` [PATCH 1/4] fsx: fix strncpy usage error Darrick J. Wong
2020-11-14 10:42 ` Christoph Hellwig
2020-11-11 0:44 ` [PATCH 2/4] fsstress: stop using attr_set Darrick J. Wong
2020-11-14 10:45 ` Christoph Hellwig
2020-11-11 0:44 ` [PATCH 3/4] fsstress: remove attr_remove Darrick J. Wong
2020-11-14 10:45 ` Christoph Hellwig
2020-11-11 0:45 ` [PATCH 4/4] fsstress: get rid of attr_list Darrick J. Wong
2020-11-14 10:47 ` Christoph Hellwig
2021-02-11 21:18 ` Darrick J. Wong
2021-02-11 21:22 ` Darrick J. Wong
2020-11-15 9:12 ` Eryu Guan [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=20201115091253.GJ3853@desktop \
--to=guan@eryu.me \
--cc=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox