From: Jonathan Corbet <corbet@lwn.net>
To: Shuah Khan <skhan@linuxfoundation.org>,
Daniel Latypov <dlatypov@google.com>,
brendanhiggins@google.com, davidgow@google.com
Cc: linux-kernel@vger.kernel.org, kunit-dev@googlegroups.com,
linux-doc@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 1/3] Documentation: kunit: remove duplicate kunit-tool.rst
Date: Fri, 24 Jun 2022 16:43:38 -0600 [thread overview]
Message-ID: <8735ft3co5.fsf@meer.lwn.net> (raw)
In-Reply-To: <2c3399e9-4f4e-a71a-4030-e4e6d72b5d4e@linuxfoundation.org>
Shuah Khan <skhan@linuxfoundation.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.
Thanks,
jon
next prev parent reply other threads:[~2022-06-24 22:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 19:56 [PATCH 1/3] Documentation: kunit: remove duplicate kunit-tool.rst Daniel Latypov
2022-06-03 19:56 ` [PATCH 2/3] Documentation: kunit: move mention of --jobs flag lower Daniel Latypov
2022-06-03 19:56 ` [PATCH 3/3] Documentation: kunit: rewrite section on .kunitconfig Daniel Latypov
2022-06-24 19:47 ` [PATCH 1/3] Documentation: kunit: remove duplicate kunit-tool.rst Jonathan Corbet
2022-06-24 19:58 ` Daniel Latypov
2022-06-24 22:36 ` Shuah Khan
2022-06-24 22:43 ` Jonathan Corbet [this message]
2022-06-24 22:51 ` Shuah Khan
2022-06-24 23:40 ` Daniel Latypov
2022-06-27 22:28 ` Jonathan Corbet
2022-06-29 16:45 ` Shuah Khan
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=8735ft3co5.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=brendanhiggins@google.com \
--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=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).