public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: libin <huawei.libin@huawei.com>
To: "Daniel K." <dk@syse.no>, <rostedt@goodmis.org>, <mingo@redhat.com>
Cc: <linux-kernel@vger.kernel.org>, <guohanjun@huawei.com>,
	<xiexiuqi@huawei.com>
Subject: Re: [PATCH] ftrace: fix a typo in comment
Date: Mon, 30 Nov 2015 18:20:06 +0800	[thread overview]
Message-ID: <565C22D6.1070505@huawei.com> (raw)
In-Reply-To: <565C1CB0.8000804@syse.no>

Sorry for my mistake. And please ignore this patch.

Thanks,
Li Bin

on 2015/11/30 17:53, Daniel K. wrote:
> On 11/30/2015 09:24 AM, Li Bin wrote:
>> s/ARCH_SUPPORT_FTARCE_OPS/ARCH_SUPPORTS_FTARCE_OPS
> How about s/FTARCE/FTRACE/ as well?
>
>
> Daniel K.
>
>
>



  reply	other threads:[~2015-11-30 10:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30  9:24 [PATCH] ftrace: fix a typo in comment Li Bin
2015-11-30  9:53 ` Daniel K.
2015-11-30 10:20   ` libin [this message]
2015-11-30 15:04 ` 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=565C22D6.1070505@huawei.com \
    --to=huawei.libin@huawei.com \
    --cc=dk@syse.no \
    --cc=guohanjun@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=xiexiuqi@huawei.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