[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ca7dd81e-5d98-c0f6-3d84-4f2cc20f4676@arm.com>
Date: Tue, 5 Nov 2019 12:29:23 +0530
From: Amit Kachhap <amit.kachhap@....com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Mark Rutland <mark.rutland@....com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
catalin.marinas@....com, deller@....de, duwe@...e.de,
James.Bottomley@...senPartnership.com, james.morse@....com,
jeyu@...nel.org, jpoimboe@...hat.com, jthierry@...hat.com,
linux-parisc@...r.kernel.org, mingo@...hat.com,
peterz@...radead.org, svens@...ckframe.org,
takahiro.akashi@...aro.org, will@...nel.org
Subject: Re: [PATCHv2 1/8] ftrace: add ftrace_init_nop()
On 11/4/19 6:41 PM, Steven Rostedt wrote:
> On Sat, 2 Nov 2019 17:49:00 +0530
> Amit Daniel Kachhap <amit.kachhap@....com> wrote:
>
>> Now that ftrace_init_nop is also an arch implemented function so it may
>> be added in Documentation/trace/ftrace-design.rst along with
>> ftrace_make_nop.
>> In general also, adding some description about patchable-function-entry
>> in kernel Documentation will be useful.
>
> I think this part is outside the scope of this patch set. Honestly, I
> need to chisel out some time to rewrite the ftrace-design document, as
> that's been long needed. But that can come at a later time. I'm
> currently rewriting some of it now, so it will be best to not waste
> effort to update a document that will soon become stale. ;-)
Yes it makes sense.
Thanks,
Amit
>
> -- Steve
>
Powered by blists - more mailing lists