From: Jonathan Corbet <corbet@lwn.net>
To: Andreas Ziegler <andreas.ziegler@fau.de>
Cc: Changbin Du <changbin.du@intel.com>,
Steven Rostedt <rostedt@goodmis.org>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Documentation: trace: improve probe documentation
Date: Mon, 23 Jul 2018 09:26:56 -0600 [thread overview]
Message-ID: <20180723092656.70333488@lwn.net> (raw)
In-Reply-To: <1531739158-31133-1-git-send-email-andreas.ziegler@fau.de>
On Mon, 16 Jul 2018 13:05:56 +0200
Andreas Ziegler <andreas.ziegler@fau.de> wrote:
> This series improves the documentation for uprobes and
> kprobes.
>
> The filename for enabling/disabling single events is 'enable',
> not 'enabled'. kprobetrace.rst lists the files present in the
> per-event directories but missed 'trigger' so far.
I've applied the pair, thanks.
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-07-23 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 11:05 [PATCH 0/2] Documentation: trace: improve probe documentation Andreas Ziegler
2018-07-16 11:05 ` [PATCH 1/2] Documentation: {u,k}probes: fix filename for event enabling Andreas Ziegler
2018-07-16 11:05 ` [PATCH 2/2] Documentation: kprobetrace: document 'trigger' file Andreas Ziegler
2018-07-23 15:26 ` Jonathan Corbet [this message]
2018-07-23 15:52 ` [PATCH 0/2] Documentation: trace: improve probe documentation Steven Rostedt
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=20180723092656.70333488@lwn.net \
--to=corbet@lwn.net \
--cc=andreas.ziegler@fau.de \
--cc=changbin.du@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tom.zanussi@linux.intel.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