linux-kernel - Re: [PATCH 1/3] Documentation: kunit: remove duplicate kunit-tool.rst

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:   Fri, 24 Jun 2022 16:40:06 -0700
From:   Daniel Latypov <dlatypov@...gle.com>
To:     Shuah Khan <skhan@...uxfoundation.org>
Cc:     Jonathan Corbet <corbet@....net>, brendanhiggins@...gle.com,
        davidgow@...gle.com, linux-kernel@...r.kernel.org,
        kunit-dev@...glegroups.com, linux-doc@...r.kernel.org
Subject: Re: [PATCH 1/3] Documentation: kunit: remove duplicate kunit-tool.rst

On Fri, Jun 24, 2022 at 3:51 PM Shuah Khan <skhan@...uxfoundation.org> wrote:
>
> On 6/24/22 4:43 PM, Jonathan Corbet wrote:
> > Shuah Khan <skhan@...uxfoundation.org> writes:
> >
> >>> So not that long ago these patches were going through Shuah...it seems
> >>> that's not happening anymore?  I can pick up kunit docs patches,
> >>> certainly.  I've taken the silence on these as assent and applied them.
> >>>
> >>
> >> I am still taking ksefltest and kunit doc patches through my tree. I wait
> >> for Brendan to ack at times. This one didn't show up in linux-kselftest
> >> list it appears.
> >>
> >> If you cc linux-kselftest and I get an ack from Brendan, I will take this
> >> through kselftest tree.
> >
> > As I said up above, I went ahead and applied them.  I can drop them
> > again if you want to carry them, just let me know.
> >
>
> Jon, yes please go ahead and drop this one. I will wait for Brendan
> to ack it. Reduces confusion in the future. Very often, there is code
> dependencies as well.
>
> Daniel, please don't skip kselftest list in the future.

Ack.
I was hoping to avoid confusion about who should apply them; looks
like it created more.

Just a note: this one has no code dependencies, so it can be applied
whenever or wherever.

Daniel