From: Steven Rostedt <rostedt@goodmis.org>
To: Daniel Bristot de Oliveira <bristot@kernel.org>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH 0/3] libtracefs documentation fixes
Date: Thu, 29 Jul 2021 15:18:52 -0400 [thread overview]
Message-ID: <20210729151852.4b59afb9@oasis.local.home> (raw)
In-Reply-To: <cover.1627568431.git.bristot@kernel.org>
On Thu, 29 Jul 2021 16:50:07 +0200
Daniel Bristot de Oliveira <bristot@kernel.org> wrote:
> I started using libtracefs last week, and I am really impressed!
>
> While learning about it, I ended up finding three small issues
> in the documentation, here they are.
>
> Daniel Bristot de Oliveira (3):
> libtracefs: Fix example in libtracefs-events-tep
> libtracefs: Fix example in libtracefs-events
> libtracefs: Fix a typo in libtracefs-files
>
>
Thanks Daniel, I'll queue these up for my next push.
-- Steve
prev parent reply other threads:[~2021-07-29 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 14:50 [PATCH 0/3] libtracefs documentation fixes Daniel Bristot de Oliveira
2021-07-29 14:50 ` [PATCH 1/3] libtracefs: Fix example in libtracefs-events-tep Daniel Bristot de Oliveira
2021-07-29 14:50 ` [PATCH 2/3] libtracefs: Fix example in libtracefs-events Daniel Bristot de Oliveira
2021-07-29 14:50 ` [PATCH 3/3] libtracefs: Fix a typo in libtracefs-files Daniel Bristot de Oliveira
2021-07-29 19:18 ` Steven Rostedt [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=20210729151852.4b59afb9@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=bristot@kernel.org \
--cc=linux-trace-devel@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;
as well as URLs for NNTP newsgroup(s).