From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jonathan Corbet <corbet@lwn•net>
Cc: Shuah Khan <skhan@linuxfoundation•org>,
Brendan Higgins <brendanhiggins@google•com>,
Daniel Latypov <dlatypov@google•com>,
Harinder Singh <sharinder@google•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: manual merge of the kunit-next tree with the jc_docs tree
Date: Tue, 11 Jan 2022 10:15:59 +1100 [thread overview]
Message-ID: <20220111101559.3f787248@canb.auug.org.au> (raw)
In-Reply-To: <20211224163707.70e04c0f@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 2742 bytes --]
Hi all,
On Fri, 24 Dec 2021 16:37:07 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Today's linux-next merge of the kunit-next tree got a conflict in:
>
> Documentation/dev-tools/kunit/start.rst
>
> between commit:
>
> c48b9ef1f794 ("Documentation: KUnit: Rewrite getting started")
>
> from the jc_docs tree and commit:
>
> 4c2911f1e140 ("kunit: tool: reconfigure when the used kunitconfig changes")
>
> from the kunit-next tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
>
> diff --cc Documentation/dev-tools/kunit/start.rst
> index a858ab009944,0a5e65540974..000000000000
> --- a/Documentation/dev-tools/kunit/start.rst
> +++ b/Documentation/dev-tools/kunit/start.rst
> @@@ -59,19 -44,23 +59,20 @@@ or ``VFAT_FS``. To run ``FAT_KUNIT_TEST
>
> CONFIG_LIST_KUNIT_TEST=y
>
> -:doc:`kunit_tool <kunit-tool>` will ensure that all config options set in
> -``.kunitconfig`` are set in the kernel ``.config`` before running the tests.
> -It'll warn you if you haven't included the dependencies of the options you're
> -using.
> +Before running the tests, kunit_tool ensures that all config options
> +set in ``.kunitconfig`` are set in the kernel ``.config``. It will warn
> +you if you have not included dependencies for the options used.
>
> - .. note ::
> - The configuration is only updated if the ``.kunitconfig`` is not a
> - subset of ``.config``. You can use tools (for example:
> - make menuconfig) to adjust other config options.
> + .. note::
> + If you change the ``.kunitconfig``, kunit.py will trigger a rebuild of the
> + ``.config`` file. But you can edit the ``.config`` file directly or with
> + tools like ``make menuconfig O=.kunit``. As long as its a superset of
> + ``.kunitconfig``, kunit.py won't overwrite your changes.
>
> -
> -Running the tests (KUnit Wrapper)
> ----------------------------------
> -
> -To make sure that everything is set up correctly, simply invoke the Python
> -wrapper from your kernel repo:
> +Running Tests (KUnit Wrapper)
> +-----------------------------
> +1. To make sure that everything is set up correctly, invoke the Python
> + wrapper from your kernel repository:
>
> .. code-block:: bash
>
This is now a conflict between the jc_docs tree and Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-01-10 23:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-24 5:37 linux-next: manual merge of the kunit-next tree with the jc_docs tree Stephen Rothwell
2022-01-10 23:15 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-24 5:32 Stephen Rothwell
2022-01-04 19:05 ` Daniel Latypov
2022-01-04 20:26 ` Brendan Higgins
2022-01-10 23:16 ` Stephen Rothwell
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=20220111101559.3f787248@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=brendanhiggins@google$(echo .)com \
--cc=corbet@lwn$(echo .)net \
--cc=dlatypov@google$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sharinder@google$(echo .)com \
--cc=skhan@linuxfoundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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