Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: abusque@efficios.com (Antoine Busque)
Subject: [lttng-dev] [PATCH lttng-ust 2/2] Doc: add LTTNG_UST_CLOCK_PLUGIN to man page
Date: Thu, 23 Jul 2015 15:37:42 -0400	[thread overview]
Message-ID: <CA+MZcXtt-hz1WyToHFe49W6iTUjuvRgm_VOn4w=MbMOxfeGarQ@mail.gmail.com> (raw)
In-Reply-To: <1437674396-13934-2-git-send-email-jonathan.rajotte-julien@efficios.com>

On Thu, Jul 23, 2015 at 1:59 PM, Jonathan Rajotte
<jonathan.rajotte-julien at efficios.com> wrote:
> +When using LTTng-tools keep in mind that lttng-sessiond uses lttng-ust clock

Maybe change to "uses lttng-ust's"

> +definition and functions. Thus LTTNG_UST_CLOCK_PLUGIN need to be define when

"needs to be defined"

> +.IP "LTTNG_UST_CLOCK_PLUGIN"
> +Used by the clock override plugin system. The environment variable is used to
> +provide the path of the shared object who will act as the clock override
> +plugin. Example can be found under doc/example/clock-override .

As per comments on previous patch, "path to", "which will", "An example" or
"Examples" and "doc/examples/" in the path.

Regards,
Antoine Busque.



  reply	other threads:[~2015-07-23 19:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 17:59 [lttng-dev] [PATCH lttng-ust 1/2] Doc: add LTTNG_UST_GETCPU_PLUGIN " Jonathan Rajotte
2015-07-23 17:59 ` [lttng-dev] [PATCH lttng-ust 2/2] Doc: add LTTNG_UST_CLOCK_PLUGIN " Jonathan Rajotte
2015-07-23 19:37   ` Antoine Busque [this message]
2015-07-23 19:32 ` [lttng-dev] [PATCH lttng-ust 1/2] Doc: add LTTNG_UST_GETCPU_PLUGIN " Antoine Busque
2015-07-23 20:02 ` [lttng-dev] [PATCH v2 " Jonathan Rajotte
2015-07-23 20:02   ` [lttng-dev] [PATCH v2 lttng-ust 2/2] Doc: add LTTNG_UST_CLOCK_PLUGIN " Jonathan Rajotte
2015-07-24  2:22     ` Mathieu Desnoyers

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='CA+MZcXtt-hz1WyToHFe49W6iTUjuvRgm_VOn4w=MbMOxfeGarQ@mail.gmail.com' \
    --to=abusque@efficios.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