From: vijai kumar <vijaikumar.kanagarajan@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v2] Add recipe for linux kselftest
Date: Fri, 29 May 2020 02:06:29 +0530 [thread overview]
Message-ID: <CALLGG_Lpg27jzzacaXTiGizo_Ryz_DLt=teWaDb+hSyURFRtbA@mail.gmail.com> (raw)
In-Reply-To: <20200528195502.t3o7wypwck4gi4tr@yssyq.m.ilbers.de>
[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]
On Fri, May 29, 2020 at 1:25 AM Baurzhan Ismagulov <ibr@radix50.net> wrote:
> 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.
>
Sure. We could use deb_debianize. Will address in v3.
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?
>
Looks good to me. Will address it in v3.
Thanks,
Vijai Kumar K
>
> With kind regards,
> Baurzhan.
>
> --
> You received this message because you are subscribed to the Google Groups
> "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to isar-users+unsubscribe@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/isar-users/20200528195502.t3o7wypwck4gi4tr%40yssyq.m.ilbers.de
> .
>
[-- Attachment #2: Type: text/html, Size: 2488 bytes --]
next prev parent reply other threads:[~2020-05-28 20:36 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
2020-05-28 20:36 ` vijai kumar [this message]
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='CALLGG_Lpg27jzzacaXTiGizo_Ryz_DLt=teWaDb+hSyURFRtbA@mail.gmail.com' \
--to=vijaikumar.kanagarajan@gmail.com \
--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