From: Steven Rostedt <rostedt@goodmis.org>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
linux-fbdev@vger.kernel.org, linux-usb@vger.kernel.org,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, Harry Wei <harryxiyou@gmail.com>,
devel@driverdev.osuosl.org, Jonathan Corbet <corbet@lwn.net>,
James Morris <jmorris@namei.org>, Ingo Molnar <mingo@redhat.com>,
linux-input@vger.kernel.org, Roy Pledge <Roy.Pledge@nxp.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
devicetree@vger.kernel.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Jiri Kosina <jikos@kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-gpio@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, Benjamin Tissoires <ben>
Subject: Re: [PATCH v3 04/27] docs: fix broken references with multiple hints
Date: Thu, 14 Jun 2018 16:27:37 +0000 [thread overview]
Message-ID: <20180614122737.4044a2b7@gandalf.local.home> (raw)
In-Reply-To: <8e28c30c9d0ba8c4f37d57adac7e12e18296a385.1528990947.git.mchehab+samsung@kernel.org>
On Thu, 14 Jun 2018 13:08:49 -0300
Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
> +++ b/Documentation/trace/events.rst
> @@ -8,7 +8,7 @@ Event Tracing
> 1. Introduction
> =======>
> -Tracepoints (see Documentation/trace/tracepoints.txt) can be used
> +Tracepoints (see Documentation/trace/tracepoints.rst) can be used
> without creating custom kernel modules to register probe functions
> using the event tracing infrastructure.
>
> diff --git a/Documentation/trace/tracepoint-analysis.rst b/Documentation/trace/tracepoint-analysis.rst
> index a4d3ff2e5efb..bef37abf4ad3 100644
> --- a/Documentation/trace/tracepoint-analysis.rst
> +++ b/Documentation/trace/tracepoint-analysis.rst
> @@ -6,7 +6,7 @@ Notes on Analysing Behaviour Using Events and Tracepoints
> 1. Introduction
> =======>
> -Tracepoints (see Documentation/trace/tracepoints.txt) can be used without
> +Tracepoints (see Documentation/trace/tracepoints.rst) can be used without
> creating custom kernel modules to register probe functions using the event
> tracing infrastructure.
>
Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
prev parent reply other threads:[~2018-06-14 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1528990947.git.mchehab+samsung@kernel.org>
2018-06-14 16:08 ` [PATCH v3 04/27] docs: fix broken references with multiple hints Mauro Carvalho Chehab
2018-06-14 16:27 ` 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=20180614122737.4044a2b7@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=Roy.Pledge@nxp.com \
--cc=airlied@linux.ie \
--cc=b.zolnierkie@samsung.com \
--cc=corbet@lwn.net \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=harryxiyou@gmail.com \
--cc=jikos@kernel.org \
--cc=jmorris@namei.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@infradead.org \
--cc=mingo@redhat.com \
--cc=robh+dt@kernel.org \
--cc=serge@hallyn.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