[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VeCHXfgXOgx_FwS197rnF6QcAstJwf4cr4g1bdkstx1xw@mail.gmail.com>
Date: Fri, 9 Jun 2017 21:23:52 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Vitaly Kuznetsov <vkuznets@...hat.com>,
devel@...uxdriverproject.org, "x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"K. Y. Srinivasan" <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Stephen Hemminger <sthemmin@...rosoft.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Jork Loeser <Jork.Loeser@...rosoft.com>,
Simon Xiao <sixiao@...rosoft.com>,
Andy Lutomirski <luto@...nel.org>
Subject: Re: [PATCH v8 10/10] tracing/hyper-v: trace hyperv_mmu_flush_tlb_others()
On Fri, Jun 9, 2017 at 9:04 PM, Steven Rostedt <rostedt@...dmis.org> wrote:
> On Fri, 9 Jun 2017 15:27:36 +0200
> Vitaly Kuznetsov <vkuznets@...hat.com> wrote:
>> +#if IS_ENABLED(CONFIG_HYPERV)
>
> Hmm, this is new to me. I know you can use IS_ENABLED() inside C code,
> but I've never seen it used for preprocessor directives. This usually
> is just:
>
> #ifdef CONFIG_HYPERV
>
> Other than that, this looks fine to me.
That is the magic of IS_ENABLED(), IS_BUILTIN() macros.
So, the code above is fine as is.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists