public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Li Wang <liwang@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 3/6] syscalls/madvise03: Convert to new test API
Date: Wed, 18 May 2016 17:04:02 +0800	[thread overview]
Message-ID: <20160518090402.GA9916@gmail.com> (raw)
In-Reply-To: <20160517162054.GC13705@rei.suse.cz>

On Tue, May 17, 2016 at 06:20:55PM +0200, Cyril Hrubis wrote:
> Hi!
> 
> I also wonder if these testcases could be moved to madvise01.

Good idea! I'd like to merge madvise0[3|4] into madvise01. But for
madvise02.c, there probably should be taken more consideration.
If that mix up the codes, I'd prefer to keep it individual.

Additionally, thanks for the comments upon, all accepted.

Li Wang

> 
> -- 
> Cyril Hrubis
> chrubis@suse.cz

  reply	other threads:[~2016-05-18  9:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12  8:49 [LTP] [PATCH 1/6] syscalls/madvise01: Convert to new test API Li Wang
2016-05-12  8:49 ` [LTP] [PATCH 2/6] syscalls/madvise02: " Li Wang
2016-05-12  8:49   ` [LTP] [PATCH 3/6] syscalls/madvise03: " Li Wang
2016-05-12  8:49     ` [LTP] [PATCH 4/6] syscalls/madvise04: " Li Wang
2016-05-12  8:49       ` [LTP] [PATCH 5/6] syscalls/madvise05: " Li Wang
2016-05-12  8:49         ` [LTP] [PATCH 6/6] syscalls/madvise06: " Li Wang
2016-05-17 17:43         ` [LTP] [PATCH 5/6] syscalls/madvise05: " Cyril Hrubis
2016-05-17 17:28       ` [LTP] [PATCH 4/6] syscalls/madvise04: " Cyril Hrubis
2016-05-17 16:20     ` [LTP] [PATCH 3/6] syscalls/madvise03: " Cyril Hrubis
2016-05-18  9:04       ` Li Wang [this message]
2016-05-19 10:12       ` Li Wang
2016-05-19 10:19         ` Cyril Hrubis
2016-05-17 15:54   ` [LTP] [PATCH 2/6] syscalls/madvise02: " Cyril Hrubis
2016-05-17 15:21 ` [LTP] [PATCH 1/6] syscalls/madvise01: " Cyril Hrubis

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=20160518090402.GA9916@gmail.com \
    --to=liwang@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox