From: Jonathan Corbet <corbet@lwn.net>
To: <lecopzer.chen@mediatek.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<mhiramat@kernel.org>, <srv_heupstream@mediatek.com>,
<yj.chiang@mediatek.com>
Subject: Re: [PATCH] Documentation: {u,k}probes: add tracing_on before tracing
Date: Fri, 7 Jun 2019 11:57:13 -0600 [thread overview]
Message-ID: <20190607115713.7b5134e2@lwn.net> (raw)
In-Reply-To: <1557397876-18153-1-git-send-email-lecopzer.chen@mediatek.com>
On Thu, 9 May 2019 18:31:16 +0800
<lecopzer.chen@mediatek.com> wrote:
> From: Lecopzer Chen <lecopzer.chen@mediatek.com>
>
> After following the document step by step, the `cat trace` can't be
> worked without enabling tracing_on and might mislead newbies about
> the functionality.
>
> Signed-off-by: Lecopzer Chen <lecopzer.chen@mediatek.com>
Applied, thanks.
jon
prev parent reply other threads:[~2019-06-07 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 10:31 [PATCH] Documentation: {u,k}probes: add tracing_on before tracing lecopzer.chen
2019-05-09 13:08 ` Masami Hiramatsu
2019-05-10 4:19 ` Lecopzer Chen
2019-06-07 17:57 ` Jonathan Corbet [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=20190607115713.7b5134e2@lwn.net \
--to=corbet@lwn.net \
--cc=lecopzer.chen@mediatek.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=yj.chiang@mediatek.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