From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/2] runtest/syscalls: add set_mempolicy*
Date: Fri, 30 Aug 2019 15:08:02 +0200 [thread overview]
Message-ID: <20190830130801.GA27587@dell5510> (raw)
In-Reply-To: <5D68F179.3000402@cn.fujitsu.com>
Hi,
> > PS: If someone want to run syscalls from LTP as many as possible, they
> > just need to run syscalls group directly.
> +1 , set_mempolicy syscall should belong to numa and syscall group.
OK, merged. + I sorted them properly, with other set_* tests in that commit.
Kind regards,
Petr
next prev parent reply other threads:[~2019-08-30 13:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 10:14 [LTP] [PATCH 1/2] runtest/syscalls: add set_mempolicy* Yang Xu
2019-08-28 10:14 ` [LTP] [PATCH 2/2] runtest/numa: add migrate_pages* Yang Xu
2019-08-29 20:41 ` Petr Vorel
2019-08-30 1:43 ` Xiao Yang
2019-08-30 10:54 ` Petr Vorel
2019-08-30 12:58 ` Petr Vorel
2019-08-28 10:25 ` [LTP] [PATCH 1/2] runtest/syscalls: add set_mempolicy* Xiao Yang
2019-08-29 20:38 ` Petr Vorel
2019-08-30 2:04 ` Xiao Yang
2019-08-30 9:50 ` Yang Xu
2019-08-30 13:08 ` Petr Vorel [this message]
2019-08-30 10:57 ` Petr Vorel
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=20190830130801.GA27587@dell5510 \
--to=pvorel@suse.cz \
--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