public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v2] Add recipe for linux kselftest
Date: Thu, 28 May 2020 21:55:02 +0200	[thread overview]
Message-ID: <20200528195502.t3o7wypwck4gi4tr@yssyq.m.ilbers.de> (raw)
In-Reply-To: <20200519110147.14281-1-Vijaikumar_Kanagarajan@mentor.com>

Hello Vijai Kumar,

On Tue, May 19, 2020 at 04:31:47PM +0530, Vijai Kumar K wrote:
> Kselftest is a set of unit and regression tests under the
> tools/testing/selftests/ directory of the Linux kernel. These are used
> for testing individual code paths in the kernel.

Thanks, this is a useful addition.

I'd suggest to address Jan's point and replace the individual commands with
deb_debianize to provide a good in-tree example of using that functionality.

To prevent bit rot, I think every component in the mainline should have a test
case. We could add the package to e.g. isar-image-debug and build e.g.
mc:qemuamd64-buster:isar-image-debug instead of
mc:qemuamd64-buster:isar-image-base.

What do you think?

With kind regards,
Baurzhan.

  parent reply	other threads:[~2020-05-28 19:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-18 12:05 [PATCH] " Vijai Kumar K
2020-05-18 15:12 ` Jan Kiszka
2020-05-18 15:57   ` vijai kumar
2020-05-18 16:06     ` Jan Kiszka
2020-05-19 11:01       ` [PATCH v2] " Vijai Kumar K
2020-05-19 11:44         ` Jan Kiszka
2020-05-28 19:55         ` Baurzhan Ismagulov [this message]
2020-05-28 20:36           ` vijai kumar
2020-05-29 10:15             ` [PATCH v3] " Vijai Kumar K
2020-10-13 10:03               ` Jan Kiszka
2020-10-14  6:18                 ` vijaikumar....@gmail.com

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=20200528195502.t3o7wypwck4gi4tr@yssyq.m.ilbers.de \
    --to=ibr@radix50.net \
    --cc=isar-users@googlegroups.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