Linux Documentation
 help / color / mirror / Atom feed
From: Eugenio Zuccarelli <eugenio.zuccarelli@gmail.com>
To: danielmaraboo@gmail.com
Cc: brendan.higgins@linux.dev, david@davidgow.net, corbet@lwn.net,
	raemoar63@gmail.com, skhan@linuxfoundation.org,
	rdunlap@infradead.org, linux-kselftest@vger.kernel.org,
	kunit-dev@googlegroups.com, workflows@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: kunit: document --summary and --failed options
Date: Mon, 26 Oct 2026 01:30:03 -0000	[thread overview]
Message-ID: <179297820301.2598507.8486986636667612321@gmail.com> (raw)
In-Reply-To: <CAMAsx6cniehFSgKz0+FRbGV=A=TGvogwx87xcqhiZNQGfeFFYQ@mail.gmail.com>

Hi Daniel,

Thanks for checking the entries against kunit.py and kunit_parser.py.

On the indentation: the continuation lines in the patch as sent use two
spaces, matching the --json and --junit items (see the raw message on
lore). It may have lost a space on the way to your tree, but please let
me know if you still see the warnings with the original.

On Assisted-by: thanks, I had missed that docs-next dropped it. v2
follows in reply, with the tool use described in the changelog instead.

Thanks,
Eugenio (Jay)

  reply	other threads:[~2026-10-26  1:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20 12:10 [PATCH] Documentation: kunit: document --summary and --failed options Eugenio Zuccarelli
2026-10-25 13:25 ` Daniel Pereira
2026-10-26  1:30   ` Eugenio Zuccarelli [this message]
2026-10-26  1:30   ` [PATCH v2] " Eugenio Zuccarelli
2026-10-26  1:46     ` Daniel Pereira

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=179297820301.2598507.8486986636667612321@gmail.com \
    --to=eugenio.zuccarelli@gmail.com \
    --cc=brendan.higgins@linux.dev \
    --cc=corbet@lwn.net \
    --cc=danielmaraboo@gmail.com \
    --cc=david@davidgow.net \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=raemoar63@gmail.com \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    --cc=workflows@vger.kernel.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