From: "Thomas Weißschuh" <linux@weissschuh.net>
To: David Gow <david@ingeniumdigital.com>
Cc: Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nsc@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Brendan Higgins <brendan.higgins@linux.dev>,
David Gow <david@davidgow.net>, Rae Moar <raemoar63@gmail.com>,
linux-kbuild@vger.kernel.org, llvm@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
kunit-dev@googlegroups.com
Subject: Re: [PATCH 2/2] kunit: qemu_configs: Add or1k / openrisc configuration
Date: Wed, 29 Apr 2026 13:14:42 +0200 [thread overview]
Message-ID: <19c00a88-ea92-4f17-afb6-9fa5da247d21@t-8ch.de> (raw)
In-Reply-To: <279a16dd-f98f-44ef-9685-44537eac2892@ingeniumdigital.com>
On 2026-04-29 18:10:58+0800, David Gow wrote:
> Le 28/04/2026 à 12:04 AM, 'Thomas Weißschuh' via KUnit Development a écrit :
> > Add a basic configuration to run kunit tests on or1k / openrisc.
> >
> > Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> > ---
>
> Thanks very much. This works well here (assuming CONFIG_KUNIT_FAULT_TESTS=n,
> and either a long timeout, or slow tests skipped, as qemu-or1k is not fast
> on my machine).
>
> Reviewed-by: David Gow <david@davidgow.net>
Thanks!
> Do we want to split the series and take this patch via kselftest/kunit, and
> the generate_compile_commands one separately, or just pick both up in the
> same tree?
They should go through the same tree as otherwise kunit.py will fail to
build the or1k architecture, as it always tries to generate
compile_commands.json.
(...)
next prev parent reply other threads:[~2026-04-29 11:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 16:04 [PATCH 0/2] kunit: qemu_configs: Add or1k / openrisc configuration Thomas Weißschuh
2026-04-27 16:04 ` [PATCH 1/2] gen_compile_commands: Ignore libgcc.a Thomas Weißschuh
2026-04-29 18:32 ` Nathan Chancellor
2026-04-27 16:04 ` [PATCH 2/2] kunit: qemu_configs: Add or1k / openrisc configuration Thomas Weißschuh
2026-04-29 10:10 ` David Gow
2026-04-29 11:14 ` Thomas Weißschuh [this message]
2026-04-29 18:30 ` Nathan Chancellor
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=19c00a88-ea92-4f17-afb6-9fa5da247d21@t-8ch.de \
--to=linux@weissschuh.net \
--cc=brendan.higgins@linux.dev \
--cc=david@davidgow.net \
--cc=david@ingeniumdigital.com \
--cc=justinstitt@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=nsc@kernel.org \
--cc=raemoar63@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