[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200928052005.GB767987@kroah.com>
Date: Mon, 28 Sep 2020 07:20:05 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Prasad Sodagudi <psodagud@...eaurora.org>
Cc: rostedt@...dmis.org, mingo@...hat.com, keescook@...omium.org,
saiprakash.ranjan@...eaurora.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, anton@...msg.org, arnd@...db.de,
catalin.marinas@....com, ccross@...roid.com, jbaron@...mai.com,
jim.cromie@...il.com, joe@...ches.com, joel@...lfernandes.org
Subject: Re: [PATCH] tracing: Add register read and write tracing support
On Sun, Sep 27, 2020 at 05:34:50PM -0700, Prasad Sodagudi wrote:
> +config TRACE_RW
> + bool "Register read/write tracing"
> + select TRACING
> + default n
n is always the default, no need to list it.
And you only did this for one arch, yet you made a generic kernel config
option, is that really wise?
thanks,
greg k-h
Powered by blists - more mailing lists