linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH 05/28] cpufreq: drop owner assignment from platform_drivers
Date: Wed, 31 Dec 2014 11:23:26 +0100	[thread overview]
Message-ID: <20141231102326.GA1461@katana> (raw)
In-Reply-To: <2262992.pVJSfL5P4D@vostro.rjw.lan>

On Mon, Dec 22, 2014 at 11:39:32PM +0100, Rafael J. Wysocki wrote:
> On Monday, December 22, 2014 07:14:56 AM Viresh Kumar wrote:
> > On 22 December 2014 at 02:44, Wolfram Sang <wsa@the-dreams.de> wrote:
> > > This platform_driver does not need to set an owner, it will be populated by the
> > > driver core.
> > >
> > > Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
> > > ---
> > > Generated with coccinelle. SmPL file is in the introductory msg. The big
> > > cleanup was pulled in this merge window. This series catches the bits fallen
> > > through. The patches shall go in via the subsystem trees.
> > >
> > >  drivers/cpufreq/ls1x-cpufreq.c | 1 -
> > >  1 file changed, 1 deletion(-)
> > >
> > > diff --git a/drivers/cpufreq/ls1x-cpufreq.c b/drivers/cpufreq/ls1x-cpufreq.c
> > > index 25fbd6a1374f..f0913eee2f50 100644
> > > --- a/drivers/cpufreq/ls1x-cpufreq.c
> > > +++ b/drivers/cpufreq/ls1x-cpufreq.c
> > > @@ -210,7 +210,6 @@ out:
> > >  static struct platform_driver ls1x_cpufreq_platdrv = {
> > >         .driver = {
> > >                 .name   = "ls1x-cpufreq",
> > > -               .owner  = THIS_MODULE,
> > >         },
> > >         .probe          = ls1x_cpufreq_probe,
> > >         .remove         = ls1x_cpufreq_remove,
> > 
> > Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> > --
> 
> OK
> 
> Wolfram, please feel free to push this through whatever tree you think is
> appropriate.

I'd prefer if you take it. However, I'll send all leftover ones to Greg,
so you can decide.


  reply	other threads:[~2014-12-31 10:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-21 21:14 [PATCH 00/28] remove .owner for most platform_drivers: the missing bits Wolfram Sang
2014-12-21 21:14 ` [PATCH 05/28] cpufreq: drop owner assignment from platform_drivers Wolfram Sang
2014-12-22  1:44   ` Viresh Kumar
2014-12-22 22:39     ` Rafael J. Wysocki
2014-12-31 10:23       ` Wolfram Sang [this message]
2015-01-30  0:12         ` Rafael J. Wysocki
2014-12-21 21:14 ` [PATCH 18/28] thermal: " Wolfram Sang
2014-12-22  3:01   ` Zhang Rui
2014-12-21 21:14 ` [PATCH 19/28] thermal: int340x_thermal: " Wolfram Sang

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=20141231102326.GA1461@katana \
    --to=wsa@the-dreams.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=viresh.kumar@linaro.org \
    /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;
as well as URLs for NNTP newsgroup(s).