From: Steven Rostedt <rostedt@goodmis.org>
To: Tzvetomir Stoyanov <tstoyanov@vmware.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v6 09/26] tools/lib/traceevent: Man page for tep_strerror()
Date: Fri, 10 May 2019 13:48:40 -0400 [thread overview]
Message-ID: <20190510134840.41d3ca77@gandalf.local.home> (raw)
In-Reply-To: <20190503091119.23399-10-tstoyanov@vmware.com>
On Fri, 3 May 2019 12:11:02 +0300
Tzvetomir Stoyanov <tstoyanov@vmware.com> wrote:
> +It as a thread safe wrapper around strerror_r(). The library function has two
> +different behaviors - POSIX and GNU specific. The _tep_strerror()_ API behaves
> +as the POSIX version - the error string is copied in the user supplied buffer.
I updated this to say "API always behaves as the POSIX version", to
remove any ambiguity.
Thanks!
-- Steve
next prev parent reply other threads:[~2019-05-10 17:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 9:10 [PATCH v6 00/26] Libtraceevent MAN pages Tzvetomir Stoyanov
2019-05-03 9:10 ` [PATCH v6 01/26] tools/lib/traceevent: Implement libtraceevent man pages Tzvetomir Stoyanov
2019-05-10 17:34 ` Steven Rostedt
2019-05-03 9:10 ` [PATCH v6 02/26] tools/lib/traceevent: Add support for man pages with multiple names Tzvetomir Stoyanov
2019-05-03 9:10 ` [PATCH v6 03/26] tools/lib/traceevent: libtraceevent man pages for tep_handler related APIs Tzvetomir Stoyanov
2019-05-03 9:10 ` [PATCH v6 04/26] tools/lib/traceevent: Man page for header_page APIs Tzvetomir Stoyanov
2019-05-03 9:10 ` [PATCH v6 05/26] tools/lib/traceevent: Man page for get/set cpus APIs Tzvetomir Stoyanov
2019-05-03 9:10 ` [PATCH v6 06/26] tools/lib/traceevent: Man page for file endian APIs Tzvetomir Stoyanov
2019-05-03 9:11 ` [PATCH v6 07/26] tools/lib/traceevent: Man page for host " Tzvetomir Stoyanov
2019-05-03 9:11 ` [PATCH v6 08/26] tools/lib/traceevent: Man page for page size APIs Tzvetomir Stoyanov
2019-05-03 9:11 ` [PATCH v6 09/26] tools/lib/traceevent: Man page for tep_strerror() Tzvetomir Stoyanov
2019-05-10 17:48 ` Steven Rostedt [this message]
2019-05-03 9:11 ` [PATCH v6 10/26] tools/lib/traceevent: Man pages for event handler APIs Tzvetomir Stoyanov
2019-05-03 9:11 ` [PATCH v6 11/26] tools/lib/traceevent: Man pages for function related libtraceevent APIs Tzvetomir Stoyanov
2019-05-03 9:11 ` [PATCH v6 12/26] tools/lib/traceevent: Man pages for registering print function Tzvetomir Stoyanov
2019-05-03 9:11 ` [PATCH v6 13/26] tools/lib/traceevent: Man page for tep_read_number() Tzvetomir Stoyanov
2019-05-03 9:11 ` [PATCH v6 14/26] tools/lib/traceevent: Man pages for event find APIs Tzvetomir Stoyanov
2019-05-03 9:11 ` [PATCH v6 15/26] tools/lib/traceevent: Man page for list events APIs Tzvetomir Stoyanov
2019-05-03 9:11 ` [PATCH v6 16/26] tools/lib/traceevent: Man pages for libtraceevent event get APIs Tzvetomir Stoyanov
2019-05-03 9:11 ` [PATCH v6 17/26] tools/lib/traceevent: Man pages find field APIs Tzvetomir Stoyanov
2019-05-03 9:11 ` [PATCH v6 18/26] tools/lib/traceevent: Man pages get field value APIs Tzvetomir Stoyanov
2019-05-03 9:11 ` [PATCH v6 19/26] tools/lib/traceevent: Man pages for print field APIs Tzvetomir Stoyanov
2019-05-03 9:11 ` [PATCH v6 20/26] tools/lib/traceevent: Man page for tep_read_number_field() Tzvetomir Stoyanov
2019-05-03 9:11 ` [PATCH v6 21/26] tools/lib/traceevent: Man pages for event fields APIs Tzvetomir Stoyanov
2019-05-03 9:11 ` [PATCH v6 22/26] tools/lib/traceevent: Man pages for event filter APIs Tzvetomir Stoyanov
2019-05-03 9:11 ` [PATCH v6 23/26] tools/lib/traceevent: Man pages for parse event APIs Tzvetomir Stoyanov
2019-05-03 9:11 ` [PATCH v6 24/26] tools/lib/traceevent: Man page for tep_parse_header_page() Tzvetomir Stoyanov
2019-05-03 9:11 ` [PATCH v6 25/26] tools/lib/traceevent: Man pages for APIs, used to extract common fields from a record Tzvetomir Stoyanov
2019-05-10 18:29 ` Steven Rostedt
2019-05-03 9:11 ` [PATCH v6 26/26] tools/lib/traceevent: Man pages for trace sequences APIs Tzvetomir Stoyanov
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=20190510134840.41d3ca77@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=tstoyanov@vmware.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;
as well as URLs for NNTP newsgroup(s).