[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <321d069a-0db3-6abd-c25e-4da46f361bd7@gmail.com>
Date: Wed, 29 Jun 2022 15:44:29 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: David Gow <davidgow@...gle.com>,
Daniel Latypov <dlatypov@...gle.com>,
Brendan Higgins <brendanhiggins@...gle.com>,
Shuah Khan <skhan@...uxfoundation.org>
Cc: kunit-dev@...glegroups.com, linux-kselftest@...r.kernel.org,
linux-kernel@...r.kernel.org,
Linux Doc Mailing List <linux-doc@...r.kernel.org>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH v2] Documentation: kunit: Cleanup run_wrapper, fix x-ref
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
Powered by blists - more mailing lists