From: Daniel Latypov <dlatypov@google.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: brendanhiggins@google.com, davidgow@google.com,
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 12:58:36 -0700 [thread overview]
Message-ID: <CAGS_qxqOZBr7Ti_pS20Qw3RLH+VjnhR5mDhJ2hyezKSo9Du-ew@mail.gmail.com> (raw)
In-Reply-To: <87pmix3ktq.fsf@meer.lwn.net>
On Fri, Jun 24, 2022 at 12:47 PM Jonathan Corbet <corbet@lwn.net> wrote:
>
> Daniel Latypov <dlatypov@google.com> writes:
>
> > The information is duplicated now in run_wrapper.rst, which was added in
> > commit 46201d47d6c4 ("Documentation: kunit: Reorganize documentation
> > related to running tests").
> >
> > You cna compare these pages here:
> > https://www.kernel.org/doc/html/v5.18/dev-tools/kunit/run_wrapper.html
> > https://www.kernel.org/doc/html/v5.18/dev-tools/kunit/kunit-tool.html
> >
> > We should have deleted it in then but it got overlooked.
> >
> > Signed-off-by: Daniel Latypov <dlatypov@google.com>
>
> 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.
Thanks!
Tbh, I'm not really sure what the status is either.
I saw that 46201d47d6c4 (which added the duplication) went through the
docs tree, so I followed suit for this.
I've been guilty of sending purely doc patches through
Shuah/-kselftest tree before, but that was mostly when there were code
change dependencies.
If it makes it simpler, we could try and agree that all kunit doc
patches go through Shuah going forward?
Shuah, Bredan: thoughts/opinions?
Daniel
next prev parent reply other threads:[~2022-06-24 19:58 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 [this message]
2022-06-24 22:36 ` Shuah Khan
2022-06-24 22:43 ` Jonathan Corbet
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=CAGS_qxqOZBr7Ti_pS20Qw3RLH+VjnhR5mDhJ2hyezKSo9Du-ew@mail.gmail.com \
--to=dlatypov@google.com \
--cc=brendanhiggins@google.com \
--cc=corbet@lwn.net \
--cc=davidgow@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).