From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Borislav Petkov <bp@alien8.de>,
cpufreq@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@suse.de>
Subject: Re: [PATCH] cpufreq, ondemand: Remove leftover debug line
Date: Mon, 13 May 2013 14:14:04 +0200 [thread overview]
Message-ID: <3026061.6K3iqZoMUx@vostro.rjw.lan> (raw)
In-Reply-To: <CAOh2x=kLJ3NVN177KTWjZikkZb8Q8RQjye4qrUT=PCdCj2jSgg@mail.gmail.com>
On Sunday, May 12, 2013 08:46:34 PM Viresh Kumar wrote:
> On Thu, May 9, 2013 at 1:04 AM, Borislav Petkov <bp@alien8.de> wrote:
> > From: Borislav Petkov <bp@suse.de>
> >
> > I don't see how the virtual address of the tuners pointer would be of
> > any help to anyone so remove it.
> >
> > Signed-off-by: Borislav Petkov <bp@suse.de>
> > ---
> > drivers/cpufreq/cpufreq_ondemand.c | 1 -
> > 1 file changed, 1 deletion(-)
> >
> > diff --git a/drivers/cpufreq/cpufreq_ondemand.c b/drivers/cpufreq/cpufreq_ondemand.c
> > index b0ffef96bf77..4b9bb5def6f1 100644
> > --- a/drivers/cpufreq/cpufreq_ondemand.c
> > +++ b/drivers/cpufreq/cpufreq_ondemand.c
> > @@ -547,7 +547,6 @@ static int od_init(struct dbs_data *dbs_data)
> > tuners->io_is_busy = should_io_be_busy();
> >
> > dbs_data->tuners = tuners;
> > - pr_info("%s: tuners %p\n", __func__, tuners);
> > mutex_init(&dbs_data->mutex);
> > return 0;
> > }
>
> Sorry for this message :(
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Applied to the linux-next branch.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2013-05-13 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 19:34 Borislav Petkov
2013-05-12 15:16 ` Viresh Kumar
2013-05-13 12:14 ` 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=3026061.6K3iqZoMUx@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®