From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org, Torsten Duwe <duwe@lst.de>
Subject: Re: [PATCH] powerpc: split ftrace bits into a separate file
Date: Tue, 22 Nov 2016 21:13:18 +0530 [thread overview]
Message-ID: <20161122154318.GA29256@naverao1-tp.localdomain> (raw)
In-Reply-To: <20161122094617.43d050f0@gandalf.local.home>
Hi Steve,
On 2016/11/22 09:46AM, Steven Rostedt wrote:
> On Tue, 22 Nov 2016 15:25:32 +0530
> "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> wrote:
>
> > No functional changes.
>
> Should have a better change log though. Why did you do this?
>
> I'm personally fine with this, as long as the powerpc maintainers are
> too.
Sure, thanks. Michael Ellerman wanted to split up entry_*.S:
https://marc.info/?l=linuxppc-embedded&m=147944810526787
I probably should have added a tag to indicate the same:
Suggested-by: Michael Ellerman <mpe@ellerman.id.au>
- Naveen
next prev parent reply other threads:[~2016-11-22 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 9:55 [PATCH] powerpc: split ftrace bits into a separate file Naveen N. Rao
2016-11-22 14:46 ` Steven Rostedt
2016-11-22 15:43 ` Naveen N. Rao [this message]
2016-11-22 15:46 ` Steven Rostedt
2016-11-22 16:35 ` Naveen N. Rao
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=20161122154318.GA29256@naverao1-tp.localdomain \
--to=naveen.n.rao@linux.vnet.ibm.com \
--cc=duwe@lst.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=rostedt@goodmis.org \
/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