From: Richard Palethorpe <rpalethorpe@suse.de>
To: Yang Xu <xuyang2018.jy@fujitsu.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v5 3/3] syscalls/statx08: Add new test
Date: Wed, 17 Nov 2021 09:48:53 +0000 [thread overview]
Message-ID: <874k8baz6v.fsf@suse.de> (raw)
In-Reply-To: <1637049352-25731-3-git-send-email-xuyang2018.jy@fujitsu.com>
Hi Yang,
Patch-set was pushed with and extra commit to clean up some style
issues. Please use "make check" in the future!
--
Thank you,
Richard.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2021-11-17 9:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 7:55 [LTP] [PATCH v5 1/3] syscalls/statx04: Skip STATX_ATTR_COMPRESSED flag when tesing xfs Yang Xu
2021-11-16 7:55 ` [LTP] [PATCH v5 2/3] syscalls/statx04: remove btrfs kernel version and add linux tags Yang Xu
2021-11-16 8:05 ` xuyang2018.jy
2021-11-16 9:49 ` Richard Palethorpe
2021-11-16 7:55 ` [LTP] [PATCH v5 3/3] syscalls/statx08: Add new test Yang Xu
2021-11-16 9:53 ` Richard Palethorpe
2021-11-17 9:48 ` Richard Palethorpe [this message]
2021-11-18 1:41 ` xuyang2018.jy
2021-11-16 9:47 ` [LTP] [PATCH v5 1/3] syscalls/statx04: Skip STATX_ATTR_COMPRESSED flag when tesing xfs Richard Palethorpe
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=874k8baz6v.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=ltp@lists.linux.it \
--cc=xuyang2018.jy@fujitsu.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