mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
	"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] cpufreq: s3c64xx: Rename index to driver_data
Date: Tue, 22 Oct 2013 00:58:58 +0200	[thread overview]
Message-ID: <14557635.AKI3PpiVcs@vostro.rjw.lan> (raw)
In-Reply-To: <CAKohpom-KBME6fa3BUmKfZSgJxYngD7RG+CD3vHHKdtWtrtOxA@mail.gmail.com>

On Monday, October 21, 2013 12:59:30 PM Viresh Kumar wrote:
> On 15 October 2013 00:06, Charles Keepax
> <ckeepax@opensource.wolfsonmicro.com> wrote:
> > The index field of cpufreq_frequency_table has been renamed to driver
> > data in this commit:
> >
> > commit 5070158804b5339c71809f5e673cea1cfacd804d
> > cpufreq: rename index as driver_data in cpufreq_frequency_table
> >
> > This patch updates the s3c64xx driver to match.
> >
> > Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> > ---
> >  drivers/cpufreq/s3c64xx-cpufreq.c |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/drivers/cpufreq/s3c64xx-cpufreq.c b/drivers/cpufreq/s3c64xx-cpufreq.c
> > index 8a72b0c..15631f9 100644
> > --- a/drivers/cpufreq/s3c64xx-cpufreq.c
> > +++ b/drivers/cpufreq/s3c64xx-cpufreq.c
> > @@ -166,7 +166,7 @@ static void __init s3c64xx_cpufreq_config_regulator(void)
> >                 if (freq->frequency == CPUFREQ_ENTRY_INVALID)
> >                         continue;
> >
> > -               dvfs = &s3c64xx_dvfs_table[freq->index];
> > +               dvfs = &s3c64xx_dvfs_table[freq->driver_data];
> >                 found = 0;
> >
> >                 for (i = 0; i < count; i++) {
> 
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> 
> @Rafael: Can you please get this in 3.12 as a bug fix?

It went in already, didn't it?

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

      reply	other threads:[~2013-10-21 22:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-14 18:36 Charles Keepax
2013-10-21  7:29 ` Viresh Kumar
2013-10-21 22:58   ` Rafael J. Wysocki [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=14557635.AKI3PpiVcs@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=patches@opensource.wolfsonmicro.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®