linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Yoann Congal <yoann.congal@smile.fr>, linux-trace-kernel@vger.kernel.org
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v3 0/3] Documentation: kprobetrace: Improve readability
Date: Tue, 24 Jan 2023 10:08:28 +0700	[thread overview]
Message-ID: <Y89LrFN0ua3p3pNE@debian.me> (raw)
In-Reply-To: <20230121225304.1711635-1-yoann.congal@smile.fr>

[-- Attachment #1: Type: text/plain, Size: 332 bytes --]

On Sat, Jan 21, 2023 at 11:53:02PM +0100, Yoann Congal wrote:
> Hi,
> 
> Version 3 of this series of small readability fixes on kprobetrace.rst.
> 

Quickly skimmed this series, it LGTM. Thanks for submitting.

Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      parent reply	other threads:[~2023-01-24  3:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-21 22:53 [PATCH v3 0/3] Documentation: kprobetrace: Improve readability Yoann Congal
2023-01-21 22:53 ` [PATCH v3 1/3] Documentation: kprobetrace: Fix some typos Yoann Congal
2023-01-21 22:53 ` [PATCH v3 2/3] Documentation: kprobetrace: Fix code block markup Yoann Congal
2023-01-21 22:53 ` [PATCH v3 3/3] Documentation: kprobetrace: Split paragraphs Yoann Congal
2023-01-21 23:31 ` [PATCH v3 0/3] Documentation: kprobetrace: Improve readability Masami Hiramatsu
2023-01-23 15:33   ` Steven Rostedt
2023-01-24 22:01     ` Jonathan Corbet
2023-01-25  7:58       ` Yoann Congal
2023-01-24  3:08 ` 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=Y89LrFN0ua3p3pNE@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=yoann.congal@smile.fr \
    /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).