linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "chengjian (D)" <cj.chengjian@huawei.com>
Cc: Peter Zijlstra <peterz@infradead.org>, <xiexiuqi@huawei.com>,
	<huawei.libin@huawei.com>, <tglx@linutronix.de>, <x86@kernel.org>,
	<linux-kernel@vger.kernel.org>, <bobo.shaobowang@huawei.com>
Subject: Re: [PATCH] x86/ftrace: use ftrace_write to simplify code
Date: Tue, 14 Jan 2020 09:13:30 -0500	[thread overview]
Message-ID: <20200114091330.0ac1b2c3@gandalf.local.home> (raw)
In-Reply-To: <8435b848-f638-978c-bbd5-459657c4b34e@huawei.com>

On Tue, 14 Jan 2020 17:20:13 +0800
"chengjian (D)" <cj.chengjian@huawei.com> wrote:

> On 2020/1/14 16:16, Peter Zijlstra wrote:
> > On Tue, Jan 14, 2020 at 01:52:17AM +0000, Cheng Jian wrote:  
> >> ftrace_write() can be used in ftrace_modify_code_direct(),
> >> that make the code more brief.
> >>
> >> Signed-off-by: Cheng Jian <cj.chengjian@huawei.com>  
> > None of the code you're patching still exists. Please see tip/master.
> >
> > .  
> 
> 
> I find these patches in TIP. My patch may not be necessary.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=768ae4406a5cab7e8702550f2446dbeb377b798d
> 
> Thank you, Peter.
> 

I was thinking that Peter's changes made it to mainline already (and I
just rebased my next merge window work on 5.5-rc6).

I should have told you this :-/

-- Steve

      reply	other threads:[~2020-01-14 14:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14  1:52 [PATCH] x86/ftrace: use ftrace_write to simplify code Cheng Jian
2020-01-14  8:16 ` Peter Zijlstra
2020-01-14  9:20   ` chengjian (D)
2020-01-14 14:13     ` 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=20200114091330.0ac1b2c3@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=bobo.shaobowang@huawei.com \
    --cc=cj.chengjian@huawei.com \
    --cc=huawei.libin@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).