lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 4 Jan 2022 15:26:20 -0500
From:   Brendan Higgins <brendanhiggins@...gle.com>
To:     Daniel Latypov <dlatypov@...gle.com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Shuah Khan <skhan@...uxfoundation.org>,
        Jonathan Corbet <corbet@....net>,
        Harinder Singh <sharinder@...gle.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: manual merge of the kunit-next tree with the jc_docs tree

On Tue, Jan 4, 2022 at 2:05 PM Daniel Latypov <dlatypov@...gle.com> wrote:
>
> On Thu, Dec 23, 2021 at 9:33 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > Hi all,
> >
> > Today's linux-next merge of the kunit-next tree got a conflict in:
> >
> >   Documentation/dev-tools/kunit/index.rst
> >
> > between commit:
> >
> >   6c6213f4a29b ("Documentation: KUnit: Rewrite main page")
> >
> > from the jc_docs tree and commit:
> >
> >   58b391d74630 ("Documentation: kunit: remove claims that kunit is a mocking framework")
> >
> > from the kunit-next tree.
> >
> > I fixed it up (I just used the former version) and can carry the fix as
>
> Thanks for this.
>
> Harinder's patch should supersede my small fixup patch.
> It wasn't clear when Harinder's patches would land in the docs tree.
>
> But it looks like my patch two files that Harinder's didn't, specifically:
>  Documentation/dev-tools/kunit/api/index.rst | 3 +--
>  Documentation/dev-tools/kunit/api/test.rst  | 3 +--
>
> Shuah, Brendan: I can send a new version of 58b391d74630 that only
> updates those two files, if wanted.
> Or we can go with Stephen's fix, which looks good to me.

I'm fine with Stephen's fix, and I am assuming that is the direction
that we already went - so probably the least likely to make waves.

So looks good to me.

Sorry about the delayed response. I was on vacation.

Cheers!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ