[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VfdE0upv1=HbNs35fcozTY6kXGpLt4tTAMVRDQZ90GHtw@mail.gmail.com>
Date: Mon, 8 Apr 2019 21:44:44 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Rajat Jain <rajatja@...gle.com>
Cc: Rajneesh Bhardwaj <rajneesh.bhardwaj@...el.com>,
Vishwanath Somayaji <vishwanath.somayaji@...el.com>,
Darren Hart <dvhart@...radead.org>,
Andy Shevchenko <andy@...radead.org>,
Platform Driver <platform-driver-x86@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Tomasz Wysocki <Wysocki@...gle.com>,
Rafael J <rafael.j.wysocki@...el.com>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
Furquan Shaikh <furquan@...gle.com>,
Evan Green <evgreen@...gle.com>,
Rajat Jain <rajatxjain@...il.com>
Subject: Re: [PATCH v3 1/3] platform/x86: intel_pmc_core: Convert to a platform_driver
On Mon, Apr 8, 2019 at 9:43 PM Rajat Jain <rajatja@...gle.com> wrote:
> On Mon, Apr 8, 2019 at 9:51 AM Andy Shevchenko
> <andy.shevchenko@...il.com> wrote:
> > On Fri, Apr 5, 2019 at 11:36 PM Rajat Jain <rajatja@...gle.com> wrote:
> > > + switch (boot_cpu_data.x86_model) {
> >
> > I didn't get why this should be boot CPU?
> > Otherwise, leave the structure and leave the x86_match_cpu() call.
>
> I didn't quite understand the concern. The x86_match_cpu() also uses
> the same boot_cpu_data that I've used, am I missing something?
It's a detail of implementation, and instead of continue using nice
helpers, you open coded the similar.
Why?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists