From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Mike Turquette <mturquette@linaro.org>
Cc: Ulf Hansson <ulf.hansson@stericsson.com>,
cpufreq@vger.kernel.org,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
Lee Jones <lee.jones@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Rickard Andersson <rickard.andersson@stericsson.com>,
Jonas Aberg <jonas.aberg@stericsson.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Philippe Begnic <philippe.begnic@st.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [RESEND PATCH 0/5] cpufreq: db8500: Rename driver and update some parts
Date: Wed, 12 Dec 2012 23:43:54 +0100 [thread overview]
Message-ID: <22600894.oJDMcB8IQb@vostro.rjw.lan> (raw)
In-Reply-To: <CAPtuhTgcmdxtG9B6L5NMyLCrhQh2o0DFkq47e_YCMoBzVhaF=g@mail.gmail.com>
On Wednesday, December 12, 2012 12:56:48 PM Mike Turquette wrote:
> On Mon, Dec 10, 2012 at 7:25 AM, Ulf Hansson <ulf.hansson@stericsson.com> wrote:
> > From: Ulf Hansson <ulf.hansson@linaro.org>
> >
> > This patchset starts by renaming the db8500 cpufreq driver to a more generic
> > name. There are new variants which rely on it too, so instead we give it a
> > family name of dbx500.
> >
> > On top of that a fixup patch for initialization of the driver and some minor
> > cleanup patches are included as well.
> >
> > These patches can be material for 3.8.
> >
> > Since some patches for the db8500 cpufreq driver has recently been merged
> > through Mike Turquette's clk tree, I decided to base these patches on top
> > of the clk-next branch. So I hope Mike is fine by merging these patches
> > through his tree.
> >
> > So I will try to collect ACKs from Rafael for the cpufreq patches. The
> > mfd patch has already been ACKED by Samuel.
> >
>
> Ulf,
>
> Just FYI clk-next has been pulled by Linus for 3.8. I can still take
> this branch once Rafael ACKs the CPUfreq bits if you want, but I think
> you have more options now that clk-next is merged in. It's up to you.
Please regard them as acked.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2012-12-12 22:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 15:25 [RESEND PATCH 0/5] cpufreq: db8500: Rename driver and update some parts Ulf Hansson
2012-12-10 15:25 ` [RESEND PATCH 1/5] cpufreq: Give driver used for dbx500 family a more generic name Ulf Hansson
2012-12-10 15:25 ` [RESEND PATCH 2/5] mfd: db8500: Update cpufreq device name Ulf Hansson
2012-12-10 15:25 ` [RESEND PATCH 3/5] cpufreq: dbx500: Move clk_get to probe Ulf Hansson
2012-12-10 15:25 ` [RESEND PATCH 4/5] cpufreq: dbx500: Minor code cleanup Ulf Hansson
2012-12-10 15:25 ` [RESEND PATCH 5/5] cpufreq: dbx500: Update file header Ulf Hansson
2012-12-11 9:15 ` [RESEND PATCH 0/5] cpufreq: db8500: Rename driver and update some parts Linus Walleij
2012-12-12 20:56 ` Mike Turquette
2012-12-12 22:43 ` Rafael J. Wysocki [this message]
2012-12-13 9:20 ` Ulf Hansson
2012-12-21 17:18 ` Mike Turquette
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=22600894.oJDMcB8IQb@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=cpufreq@vger.kernel.org \
--cc=jonas.aberg@stericsson.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=philippe.begnic@st.com \
--cc=rickard.andersson@stericsson.com \
--cc=ulf.hansson@linaro.org \
--cc=ulf.hansson@stericsson.com \
--cc=vincent.guittot@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).