From mboxrd@z Thu Jan 1 00:00:00 1970 From: rostedt@goodmis.org (Steven Rostedt) Date: Mon, 1 Oct 2018 11:14:06 -0400 Subject: [PATCH v3 1/4] DYNAMIC_FTRACE configurable with and without REGS In-Reply-To: <20181001151037.GB2634@lst.de> References: <20181001140910.086E768BC7@newverein.lst.de> <20181001141643.331EE68BC7@newverein.lst.de> <20181001150353.GA2634@lst.de> <20181001151037.GB2634@lst.de> Message-ID: <20181001111406.0c799813@gandalf.local.home> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, 1 Oct 2018 17:10:37 +0200 Torsten Duwe wrote: > On Mon, Oct 01, 2018 at 05:06:06PM +0200, Ard Biesheuvel wrote: > > On 1 October 2018 at 17:03, Torsten Duwe wrote: > > > On Mon, Oct 01, 2018 at 04:52:27PM +0200, Ard Biesheuvel wrote: > > >> > > >> I guess we now have Kbuild/Kconfig support for this, no? I mean, we > > >> can now show/hide options depending on the capabilities of the > > >> toolchain. > > > > > > Config options depending on flags availability? > > > > > Yes. Note that 'make menuconfig' now prints the compiler version at > > the top, and kconfig options can now 'depend' on compiler features, > > Ah, cool, got it. So unless anyone else thinks this patch is useful, > feel free to disregard it ;-) Point taken. > Yes, please don't apply this patch. Have the build system figure out if the tool chain can handle it or not. -- Steve