From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] Which LTP tag should be used for kernel 4.4 test
Date: Mon, 5 Sep 2016 07:07:35 -0400 (EDT) [thread overview]
Message-ID: <469851347.1788700.1473073655715.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAE6rn=Prc-_D22_hLuuMED9XqDLaNEKAytGbAVGG+0EONyZAfg@mail.gmail.com>
----- Original Message -----
> From: "张旭" <zhang.vax@gmail.com>
> To: ltp@lists.linux.it
> Sent: Friday, 2 September, 2016 11:47:22 AM
> Subject: [LTP] Which LTP tag should be used for kernel 4.4 test
>
> Hi,
>
> I want to use LTP for testing a kernel based version 4.4. Need I download
> some tag or latest LTP tag(20160510) for kernel 4.4 test?
Hi,
you can use latest tagged release or latest git tree. LTP aims
to skip tests not applicable to currently running kernel/config/hw/arch/etc.
by making various checks in setup phase of testcases and terminating with
TCONF ret code if conditions are not met.
Regards,
Jan
prev parent reply other threads:[~2016-09-05 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 9:47 [LTP] Which LTP tag should be used for kernel 4.4 test =?unknown-8bit?b?5byg5pet?=
2016-09-05 11:07 ` Jan Stancek [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=469851347.1788700.1473073655715.JavaMail.zimbra@redhat.com \
--to=jstancek@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