[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <df9b5a82-5f00-f3ec-14cf-0b212be2a7a7@quicinc.com>
Date: Fri, 7 Jan 2022 10:40:05 +0530
From: Sai Prakash Ranjan <quic_saipraka@...cinc.com>
To: Steven Rostedt <rostedt@...dmis.org>
CC: Will Deacon <will@...nel.org>,
Catalin Marinas <catalin.marinas@....com>,
Marc Zyngier <maz@...nel.org>, Arnd Bergmann <arnd@...db.de>,
gregkh <gregkh@...uxfoundation.org>, <quic_psodagud@...cinc.com>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-arm-msm@...r.kernel.org>,
Prasad Sodagudi <psodagud@...eaurora.org>
Subject: Re: [PATCHv6 4/5] tracing: Add register read/write tracing support
Hi Steve,
On 1/6/2022 11:48 PM, Steven Rostedt wrote:
> This should not be in the kernel/trace directory. It should be in the
Hmm these are called from low level generic io header file
(include/asm-generic/) where
we wouldn't have any Kconfig to control this feature flexibly and as we
can have this as
a generic feature selectable by other architectures, wouldn't this be
suited in kernel/trace?
I thought you were ok with the folder structure in the initial versions
of the series?
Thanks,
Sai
Powered by blists - more mailing lists