From: Bagas Sanjaya <bagasdotme@gmail.com>
To: David Gow <davidgow@google.com>,
Daniel Latypov <dlatypov@google.com>,
Brendan Higgins <brendanhiggins@google.com>,
Shuah Khan <skhan@linuxfoundation.org>
Cc: kunit-dev@googlegroups.com, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v2] Documentation: kunit: Cleanup run_wrapper, fix x-ref
Date: Wed, 29 Jun 2022 15:44:29 +0700 [thread overview]
Message-ID: <321d069a-0db3-6abd-c25e-4da46f361bd7@gmail.com> (raw)
In-Reply-To: <20220629040605.2395481-1-davidgow@google.com>
On 6/29/22 11:06, David Gow wrote:
> +This means that for most architectures, running under qemu is as simple as:
> +
> +.. code-block:: bash
> +
> + ./tools/testing/kunit/kunit.py run --arch=x86_64
> +
> +When cross-compiling, we'll likely need to specify a different toolchain, for
> +example:
> +
> +.. code-block:: bash
> +
> + ./tools/testing/kunit/kunit.py run \
> + --arch=s390 \
> + --cross_compile=s390x-linux-gnu-
> +
nit: s/we'll/you'll/
Otherwise looks OK.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-06-29 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 10:15 [PATCH] Documentation: kunit: Cleanup run_wrapper, fix x-ref David Gow
2022-06-28 0:44 ` Bagas Sanjaya
2022-06-29 4:06 ` [PATCH v2] " David Gow
2022-06-29 8:44 ` Bagas Sanjaya [this message]
2022-06-29 9:05 ` David Gow
2022-06-29 12:55 ` Jonathan Corbet
2022-07-06 18:40 ` Brendan Higgins
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=321d069a-0db3-6abd-c25e-4da46f361bd7@gmail.com \
--to=bagasdotme@gmail.com \
--cc=brendanhiggins@google.com \
--cc=corbet@lwn.net \
--cc=davidgow@google.com \
--cc=dlatypov@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=skhan@linuxfoundation.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).