[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181001111406.0c799813@gandalf.local.home>
Date: Mon, 1 Oct 2018 11:14:06 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Torsten Duwe <duwe@....de>
Cc: Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
Will Deacon <will.deacon@....com>,
Catalin Marinas <catalin.marinas@....com>,
Julien Thierry <julien.thierry@....com>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Ingo Molnar <mingo@...hat.com>, Arnd Bergmann <arnd@...db.de>,
AKASHI Takahiro <takahiro.akashi@...aro.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
live-patching@...r.kernel.org
Subject: Re: [PATCH v3 1/4] DYNAMIC_FTRACE configurable with and without
REGS
On Mon, 1 Oct 2018 17:10:37 +0200
Torsten Duwe <duwe@....de> wrote:
> On Mon, Oct 01, 2018 at 05:06:06PM +0200, Ard Biesheuvel wrote:
> > On 1 October 2018 at 17:03, Torsten Duwe <duwe@....de> 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
Powered by blists - more mailing lists