linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Gow <davidgow@google.com>
To: Greg Thelen <gthelen@google.com>
Cc: Brendan Higgins <brendanhiggins@google.com>,
	"open list:KERNEL SELFTEST FRAMEWORK" 
	<linux-kselftest@vger.kernel.org>,
	KUnit Development <kunit-dev@googlegroups.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	clang-built-linux@googlegroups.com
Subject: Re: [PATCH] kunit: add --make_options
Date: Thu, 27 Feb 2020 10:54:56 -0800	[thread overview]
Message-ID: <CABVgOSkdphVaWhL1bBpC-vBgJ5pS144wD_g588o2_xxHXd=Ngg@mail.gmail.com> (raw)
In-Reply-To: <20200227063134.261636-1-gthelen@google.com>

On Wed, Feb 26, 2020 at 10:31 PM 'Greg Thelen' via KUnit Development
<kunit-dev@googlegroups.com> wrote:
>
> The kunit.py utility builds an ARCH=um kernel and then runs it.  Add
> optional --make_options flag to kunit.py allowing for the operator to
> specify extra build options.
>
> This allows use of the clang compiler for kunit:
>   tools/testing/kunit/kunit.py run --defconfig \
>     --make_options CC=clang --make_options HOSTCC=clang
>
> Signed-off-by: Greg Thelen <gthelen@google.com>

Tested-by: David Gow <davidgow@google.com>

Nice! This worked for me with all of the options I tried (and it's
great to see KUnit working on clang builds!)

-- David

  parent reply	other threads:[~2020-02-27 18:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27  6:31 [PATCH] kunit: add --make_options Greg Thelen
2020-02-27 18:49 ` Brendan Higgins
2020-02-27 18:54 ` David Gow [this message]
2020-02-29  1:53 ` Nathan Chancellor
2020-03-13 20:24   ` shuah
2020-03-14  6:24     ` Greg Thelen
2020-03-23 15:09       ` shuah

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='CABVgOSkdphVaWhL1bBpC-vBgJ5pS144wD_g588o2_xxHXd=Ngg@mail.gmail.com' \
    --to=davidgow@google.com \
    --cc=brendanhiggins@google.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=gthelen@google.com \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    /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).