From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Sadiya Kazi <sadiyakazi@google.com>
Cc: brendanhiggins@google.com, davidgow@google.com,
skhan@linuxfoundation.org, corbet@lwn.net, mairacanal@riseup.net,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel test robot <lkp@intel.com>,
Daniel Latypov <dlatypov@google.com>
Subject: Re: [PATCH v4] Documentation: kunit: Add CLI args for kunit_tool
Date: Tue, 26 Jul 2022 16:15:23 +0700 [thread overview]
Message-ID: <Yt+wq+xo2Tp6oEF/@debian.me> (raw)
In-Reply-To: <20220726041250.1905521-1-sadiyakazi@google.com>
On Tue, Jul 26, 2022 at 04:12:50AM +0000, Sadiya Kazi wrote:
> Some kunit_tool command line arguments are missing in run_wrapper.rst.
> Document them.
>
> Reported-by: Bagas Sanjaya <bagasdotme@gmail.com>
> Reported-by: kernel test robot <lkp@intel.com>
> Reviewed-by: David Gow <davidgow@google.com>
> Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
> Reviewed-by: Daniel Latypov <dlatypov@google.com>
> Reviewed-by: Maíra Canal <mairacanal@riseup.net>
> Signed-off-by: Sadiya Kazi <sadiyakazi@google.com>
I think Reported-by should only be used when submitting patches that
fixes build warnings/failure pointed to the code that is already in the
tree (like mainline).
Otherwise, the documentation builds succesfully without new warnings.
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
Tested-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2022-07-26 9:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 4:12 [PATCH v4] Documentation: kunit: Add CLI args for kunit_tool Sadiya Kazi
2022-07-26 9:15 ` Bagas Sanjaya [this message]
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=Yt+wq+xo2Tp6oEF/@debian.me \
--to=bagasdotme@gmail.com \
--cc=brendanhiggins@google.com \
--cc=corbet@lwn.net \
--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=linux-kselftest@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mairacanal@riseup.net \
--cc=sadiyakazi@google.com \
--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