From: <nobuhiro1.iwamatsu@toshiba.co.jp>
To: <jan.kiszka@siemens.com>, <vijaikumar.kanagarajan@gmail.com>,
<cip-dev@lists.cip-project.org>, <Chris.Paterson2@renesas.com>,
<pavel@denx.de>
Subject: Re: [cip-dev] Linux-cip: Kselftest plans
Date: Mon, 16 Mar 2020 22:49:05 +0000 [thread overview]
Message-ID: <OSAPR01MB36676897A7976E3D6079ECDE92F90@OSAPR01MB3667.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <8cc7afeb-409b-3dee-df4b-e6a63f979723@siemens.com>
Hi all,
> -----Original Message-----
> From: Jan Kiszka [mailto:jan.kiszka@siemens.com]
> Sent: Tuesday, March 17, 2020 12:27 AM
> To: vijai kumar <vijaikumar.kanagarajan@gmail.com>;
> cip-dev@lists.cip-project.org; Chris Paterson
> <Chris.Paterson2@renesas.com>; iwamatsu nobuhiro(岩松 信洋 ○ＳＷＣ□
> ＯＳＴ) <nobuhiro1.iwamatsu@toshiba.co.jp>; Pavel Machek
> <pavel@denx.de>
> Subject: Re: [cip-dev] Linux-cip: Kselftest plans
>
> On 06.03.20 09:21, vijai kumar wrote:
> > Hi All,
> >
> > Is kselftest maintained in the cip-kernel tree? I do see some
> > branch[1] maintained by Nobuhiro-san for kselftest, but it's out of
> > 5.6 linux tree.
> >
> > The reason being to gather collective thoughts about the plan for
> > kselftest based tests for cip kernel. Are there any existing or future
> > plans for using kselftest for testing cip kernels? If so are we going
> > to use the latest tree from upstream or plan to fix/backport test
> > cases to current cip kernel versions?
I am now implementing LAVA's kselftest. This kselftest uses kseflftest included in the latest kernel.
There are no plans to backport tests to 4.4 or 4.19. I believe that ksefltest included in the CIP kernel
is inadequate in function and difficult to use as it is.
I suggest using a new kernel test that incorporates the latest tests.
Best regards,
Nobuhiro
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev
next prev parent reply other threads:[~2020-03-16 22:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 8:21 [cip-dev] Linux-cip: Kselftest plans vijai kumar
2020-03-16 15:26 ` Jan Kiszka
2020-03-16 22:49 ` nobuhiro1.iwamatsu [this message]
2020-03-17 8:00 ` vijai kumar
2020-03-19 21:19 ` Ben Hutchings
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=OSAPR01MB36676897A7976E3D6079ECDE92F90@OSAPR01MB3667.jpnprd01.prod.outlook.com \
--to=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=Chris.Paterson2@renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.com \
--cc=pavel@denx.de \
--cc=vijaikumar.kanagarajan@gmail.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;
as well as URLs for NNTP newsgroup(s).