From: Darren Hart <dvhart@infradead.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Rajneesh Bhardwaj <rajneesh.bhardwaj@intel.com>,
platform-driver-x86@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Olof Johansson <olof@lixom.net>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
dbasehore@google.com, vishwanath.somayaji@intel.com
Subject: Re: [PATCH v6] platform:x86: Add PMC Driver for Intel Core SoC
Date: Wed, 25 May 2016 14:04:03 -0700 [thread overview]
Message-ID: <20160525210403.GD109010@f23x64.localdomain> (raw)
In-Reply-To: <CAHp75Vcqxreujm9+D2JpAGkbyYZJ+uvKXjcSb_Dqcs96Y0n2_Q@mail.gmail.com>
On Wed, May 25, 2016 at 11:37:21PM +0300, Andy Shevchenko wrote:
> On Wed, May 25, 2016 at 11:13 PM, Darren Hart <dvhart@infradead.org> wrote:
> > On Wed, May 25, 2016 at 11:14:52PM +0530, Rajneesh Bhardwaj wrote:
>
> > Hi Rajneesh,
> >
> > Unfortunately during my build test, this introduced a new warning to the build:
> >
> > drivers/platform/x86/intel_pmc_core.c:201:19: warning: ‘intel_pmc_core_init’
> > defined but not used [-Wunused-function]
> > static int __init intel_pmc_core_init(void)
> >
> > After the removal of the module stuff, the driver needed a device_initcall, or
> > the macro equivalent, consider:
> >
> > $ git diff
> > diff --git a/drivers/platform/x86/intel_pmc_core.c b/drivers/platform/x86/intel_pmc_core.c
> > index c834281..f6a29b9 100644
> > --- a/drivers/platform/x86/intel_pmc_core.c
> > +++ b/drivers/platform/x86/intel_pmc_core.c
> > @@ -198,7 +198,4 @@ static struct pci_driver intel_pmc_core_driver = {
>
> > .remove = NULL, /* not a hot-plug capable driver */
>
> Since it requires an update I would suggest to remove above line completely.
Indeed, thank you Andy.
--
Darren Hart
Intel Open Source Technology Center
prev parent reply other threads:[~2016-05-25 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 17:44 Rajneesh Bhardwaj
2016-05-25 20:13 ` Darren Hart
2016-05-25 20:37 ` Andy Shevchenko
2016-05-25 21:04 ` Darren Hart [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160525210403.GD109010@f23x64.localdomain \
--to=dvhart@infradead.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=dbasehore@google.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rajneesh.bhardwaj@intel.com \
--cc=tglx@linutronix.de \
--cc=vishwanath.somayaji@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®