All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avinesh Kumar <akumar@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 0/6] Convert utime tests to new LTP API
Date: Thu, 23 Jun 2022 13:32:09 +0530	[thread overview]
Message-ID: <20220623080215.24186-1-akumar@suse.de> (raw)

Hi,
Thank you for the feedback on v1 patches, I have made the requested
changes.

Thanks,
Avinesh

Avinesh Kumar (6):
  Rewrite utime01.c using new LTP API
  Rewrite utime02.c using new LTP API
  utime03.c: Remove unnecessary header includes
  Rewrite utime04.c using new LTP API
  Rewrite utime05.c using new LTP API
  Rewrite utime06.c using new LTP API

 testcases/kernel/syscalls/utime/utime01.c | 263 +++++---------------
 testcases/kernel/syscalls/utime/utime02.c | 283 ++++++----------------
 testcases/kernel/syscalls/utime/utime03.c |   2 -
 testcases/kernel/syscalls/utime/utime04.c | 203 +++-------------
 testcases/kernel/syscalls/utime/utime05.c | 213 +++-------------
 testcases/kernel/syscalls/utime/utime06.c | 188 ++++----------
 6 files changed, 243 insertions(+), 909 deletions(-)

-- 
2.36.1


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

             reply	other threads:[~2022-06-23  8:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23  8:02 Avinesh Kumar [this message]
2022-06-23  8:02 ` [LTP] [PATCH v2 1/6] Rewrite utime01.c using new LTP API Avinesh Kumar
2022-07-04 13:13   ` Richard Palethorpe
2022-06-23  8:02 ` [LTP] [PATCH v2 2/6] Rewrite utime02.c " Avinesh Kumar
2022-07-04 13:22   ` Richard Palethorpe
2022-06-23  8:02 ` [LTP] [PATCH v2 3/6] utime03.c: Remove unnecessary header includes Avinesh Kumar
2022-07-04 13:25   ` Richard Palethorpe
2022-06-23  8:02 ` [LTP] [PATCH v2 4/6] Rewrite utime04.c using new LTP API Avinesh Kumar
2022-07-04 13:31   ` Richard Palethorpe
2022-06-23  8:02 ` [LTP] [PATCH v2 5/6] Rewrite utime05.c " Avinesh Kumar
2022-07-04 13:35   ` Richard Palethorpe
2022-06-23  8:02 ` [LTP] [PATCH v2 6/6] Rewrite utime06.c " Avinesh Kumar
2022-07-04 13:47   ` 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=20220623080215.24186-1-akumar@suse.de \
    --to=akumar@suse.de \
    --cc=ltp@lists.linux.it \
    /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.