[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1497034433.12817.17.camel@tiscali.nl>
Date: Fri, 09 Jun 2017 20:53:53 +0200
From: Paul Bolle <pebolle@...cali.nl>
To: Steven Rostedt <rostedt@...dmis.org>,
Andy Shevchenko <andy.shevchenko@...il.com>
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, 2017-06-09 at 14:32 -0400, Steven Rostedt wrote:
> I'm sure it works, but it just adds one more way of doing the same
> thing. I thought that was what perl was always criticized for, and why
> people usually prefer python. Don't get me wrong, I prefer oysters over
> snakes. But I just wanted to point out the lack of consistency here.
A major benefit is that
#if IS_ENABLED(CONFIG_HYPERV)
is shorter than
#if defined(CONFIG_HYPERV) || defined(CONFIG_HYPERV_MODULE)
and less prone to typos.
Paul Bolle
Powered by blists - more mailing lists