All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: tracing.rst neglects to document syntax of trace-events files
Date: Tue, 18 Jan 2022 09:23:50 +0100	[thread overview]
Message-ID: <87zgntpi3t.fsf@dusky.pond.sub.org> (raw)

Almost[*] all trace-events files start with this line:

    # See docs/devel/tracing.rst for syntax documentation.

But I can't find syntax documentation there.


[*] Exceptions:
    $ git-ls-files \*/trace-events| xargs fgrep -L '# See docs/devel/tracing.rst for syntax documentation.'
    ebpf/trace-events
    hw/core/trace-events
    hw/hyperv/trace-events
    hw/mips/trace-events
    hw/net/can/trace-events
    hw/nubus/trace-events
    hw/nvme/trace-events
    hw/remote/trace-events
    hw/sh4/trace-events
    hw/ssi/trace-events
    target/arm/hvf/trace-events
    target/riscv/trace-events
    target/s390x/kvm/trace-events



             reply	other threads:[~2022-01-18  8:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18  8:23 Markus Armbruster [this message]
2022-01-18  9:02 ` tracing.rst neglects to document syntax of trace-events files Daniel P. Berrangé
2022-01-26 13:11   ` Stefan Hajnoczi

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=87zgntpi3t.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.