[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1609081008250.5647@nanos>
Date: Thu, 8 Sep 2016 10:21:34 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Fenghua Yu <fenghua.yu@...el.com>
cc: "H. Peter Anvin" <h.peter.anvin@...el.com>,
Ingo Molnar <mingo@...e.hu>, Tony Luck <tony.luck@...el.com>,
Peter Zijlstra <peterz@...radead.org>,
Tejun Heo <tj@...nel.org>, Borislav Petkov <bp@...e.de>,
Stephane Eranian <eranian@...gle.com>,
Marcelo Tosatti <mtosatti@...hat.com>,
David Carrillo-Cisneros <davidcc@...gle.com>,
Shaohua Li <shli@...com>,
Ravi V Shankar <ravi.v.shankar@...el.com>,
Vikas Shivappa <vikas.shivappa@...ux.intel.com>,
Sai Prakhya <sai.praneeth.prakhya@...el.com>,
linux-kernel <linux-kernel@...r.kernel.org>, x86 <x86@...nel.org>
Subject: Re: [PATCH v2 04/33] drivers/base/cacheinfo.c: Export some cacheinfo
functions for others to use
On Thu, 8 Sep 2016, Fenghua Yu wrote:
> From: Fenghua Yu <fenghua.yu@...el.com>
>
> We use ci_cpu_cacheinfo in CAT. Export this function for CAT to reuse.
So ci_cpu_cacheinfo is a function? AFAICT it's a struct.
> +#define ci_cacheinfo(cpu) (&per_cpu(ci_cpu_cacheinfo, cpu))
Why a define and not an inline? &per_cpu should be per_cpu_ptr ....
And a define is not a function either and certainly that whole thing has
nothing to do with an export.
Furthermore $subject talks about some functions. I still have to see one.
It's an art to get a onliner patch screwed up in more than one way so
badly.
No bisquit!
tglx
Powered by blists - more mailing lists