public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>,
	isar-users@googlegroups.com
Subject: Re: [PATCH v4] Add recipe for linux kselftest
Date: Thu, 6 May 2021 15:20:46 +0300	[thread overview]
Message-ID: <9a24de2f-b673-e0bd-8ed4-33136524f07c@ilbers.de> (raw)
In-Reply-To: <20201102072511.26675-1-Vijaikumar_Kanagarajan@mentor.com>

02.11.2020 10:25, 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.
>
> Kselftest is not debianized and is not available as part of the official
> Debian repository.
>
> This patch provides a recipe to build kselftest from the linux source of
> your choice.
>
> Sometimes developers/testers tend to use the latest version of selftests
> from Linux upstream stable releases for testing and hence the need for a
> separate recipe instead of being part of the linux recipe of ISAR.
>
> Some kselftest test cases build are known to break in certain linux
> versions, this has to be addressed upstream. Right now kselftest build
> succeeds even if atleast one of the testcase case build succeeds.
>
> You can change that by setting KSELFTEST_FORCE_TARGETS=1.
>
> TARGETS, TARGETS_SKIP, FORCE_TARGETS can be set using the appropriate
> KSELFTEST_* recipe variable.
>
> Signed-off-by: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>

Applied to next, thanks.

-- 
Anton Mikanovich
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov


      parent reply	other threads:[~2021-05-06 12:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02  7:25 Vijai Kumar K
2020-11-04 20:44 ` Henning Schild
2020-11-05  6:17   ` vijaikumar....@gmail.com
2020-11-06 13:38     ` Henning Schild
2020-11-26 18:38       ` vijaikumar....@gmail.com
2021-02-08 15:33         ` Anton Mikanovich
2021-02-10  6:34           ` vijaikumar....@gmail.com
2021-02-10 10:21             ` Henning Schild
2021-02-15 15:16               ` Baurzhan Ismagulov
2021-02-18  5:11                 ` vijaikumar....@gmail.com
2021-03-30  9:11                   ` vijai kumar
2021-04-22 11:49                     ` vijaikumar....@gmail.com
2021-04-26 13:40                     ` Baurzhan Ismagulov
2021-05-06 12:20 ` Anton Mikanovich [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=9a24de2f-b673-e0bd-8ed4-33136524f07c@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=Vijaikumar_Kanagarajan@mentor.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