Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Tales Lelo da Aparecida <tales.aparecida@gmail.com>
To: Sadiya Kazi <sadiyakazi@google.com>, David Gow <davidgow@google.com>
Cc: Trevor Woerner <twoerner@gmail.com>,
	siqueirajordao@riseup.net, mwen@igalia.com,
	andrealmeid@riseup.net, mairacanal@riseup.net,
	Isabella Basso <isabbasso@riseup.net>,
	magalilemes00@gmail.com, kunit-dev@googlegroups.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, brendanhiggins@google.com,
	corbet@lwn.net
Subject: Re: [PATCH 0/4] Documentation: KUnit: minor fixes
Date: Thu, 18 Aug 2022 15:20:48 -0300	[thread overview]
Message-ID: <03535c9e-d3e7-eeca-2650-2ecf7ab4c34e@gmail.com> (raw)
In-Reply-To: <20220813042055.136832-1-tales.aparecida@gmail.com>

On 13/08/2022 01:20, Tales Aparecida wrote:
> Hi,
> 
> This is a short series of minor fixes to the Kunit documentation,
> they probably can be squashed but I suppose it's easier
> to review them individually.
> 
> Thanks for any feedbacks,
> Tales
> 
> Tales Aparecida (4):
>    Documentation: kunit: fix trivial typo
>    Documentation: Kunit: Fix inconsistent titles
>    Documentation: KUnit: Fix non-uml anchor
>    Documentation: Kunit: Add ref for other kinds of tests
> 
>   Documentation/dev-tools/kunit/architecture.rst | 4 ++--
>   Documentation/dev-tools/kunit/faq.rst          | 8 +++++---
>   Documentation/dev-tools/kunit/index.rst        | 2 ++
>   Documentation/dev-tools/kunit/run_wrapper.rst  | 4 +++-
>   Documentation/dev-tools/kunit/usage.rst        | 4 ++--
>   5 files changed, 14 insertions(+), 8 deletions(-)
> 

Hello,

Thanks for the reviews, everyone!
Should I send a V2 with squashed commits or will a committer handle that?

Kind regards,
Tales

      parent reply	other threads:[~2022-08-18 18:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-13  4:20 [PATCH 0/4] Documentation: KUnit: minor fixes Tales Aparecida
2022-08-13  4:20 ` [PATCH 1/4] Documentation: kunit: fix trivial typo Tales Aparecida
2022-08-13  7:03   ` David Gow
2022-08-17  6:41   ` Sadiya Kazi
2022-08-13  4:20 ` [PATCH 2/4] Documentation: Kunit: Fix inconsistent titles Tales Aparecida
2022-08-13  7:04   ` David Gow
2022-08-17  6:46   ` Sadiya Kazi
2022-08-13  4:20 ` [PATCH 3/4] Documentation: KUnit: Fix non-uml anchor Tales Aparecida
2022-08-13  7:04   ` David Gow
2022-08-13  4:20 ` [PATCH 4/4] Documentation: Kunit: Add ref for other kinds of tests Tales Aparecida
2022-08-13  7:04   ` David Gow
2022-08-15 16:51 ` [PATCH 0/4] Documentation: KUnit: minor fixes André Almeida
2022-08-18 18:20 ` Tales Lelo da Aparecida [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=03535c9e-d3e7-eeca-2650-2ecf7ab4c34e@gmail.com \
    --to=tales.aparecida@gmail.com \
    --cc=20220813042055.136832-1-tales.aparecida@gmail.com \
    --cc=andrealmeid@riseup.net \
    --cc=brendanhiggins@google.com \
    --cc=corbet@lwn.net \
    --cc=davidgow@google.com \
    --cc=isabbasso@riseup.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=magalilemes00@gmail.com \
    --cc=mairacanal@riseup.net \
    --cc=mwen@igalia.com \
    --cc=sadiyakazi@google.com \
    --cc=siqueirajordao@riseup.net \
    --cc=twoerner@gmail.com \
    /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