From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Stephen Warren <swarren@wwwdotorg.org>,
Thierry Reding <thierry.reding@gmail.com>,
Alexandre Courbot <gnurou@gmail.com>,
linux-tegra@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: tegra20: remove superfluous CONFIG_PM ifdefs
Date: Mon, 05 Oct 2015 22:46:23 +0200 [thread overview]
Message-ID: <2839016.SNCn424N2T@vostro.rjw.lan> (raw)
In-Reply-To: <2371290.4u0K8mkgaF@vostro.rjw.lan>
On Wednesday, September 09, 2015 10:14:50 PM Rafael J. Wysocki wrote:
> On Wednesday, September 09, 2015 12:36:39 PM Bartlomiej Zolnierkiewicz wrote:
> >
> > Hi,
> >
> > On Wednesday, September 09, 2015 03:13:45 AM Rafael J. Wysocki wrote:
> > > On Tuesday, September 08, 2015 07:13:23 PM Bartlomiej Zolnierkiewicz wrote:
> > > > CONFIG_PM ifdefs are superfluous and can be removed.
> > > >
> > > > Cc: Stephen Warren <swarren@wwwdotorg.org>
> > > > Cc: Thierry Reding <thierry.reding@gmail.com>
> > > > Cc: Alexandre Courbot <gnurou@gmail.com>
> > > > Signed-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> > >
> > > What tree does this apply to?
> >
> > It applies fine to both next (next-20150909 branch) and current Linus'
> > tree (top commit is a794b4f).
>
> OK
>
> My cpufreq branch has not acquired tegra20-cpufreq.c yet, so I'll apply this
> one when -rc1 is out. Or please ask whoever merged that driver to apply it
> earlier if you want to.
Applied now, thanks!
Rafael
next prev parent reply other threads:[~2015-10-05 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 17:13 Bartlomiej Zolnierkiewicz
2015-09-09 1:13 ` Rafael J. Wysocki
2015-09-09 10:36 ` Bartlomiej Zolnierkiewicz
2015-09-09 20:14 ` Rafael J. Wysocki
2015-10-05 20:46 ` Rafael J. Wysocki [this message]
2015-09-09 2:27 ` Viresh Kumar
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=2839016.SNCn424N2T@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=b.zolnierkie@samsung.com \
--cc=gnurou@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--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
all inboxes | Powered by JetHome®