From: Simon Horman <horms@verge.net.au>
To: Stratos Karafotis <stratosk@semaphore.gr>
Cc: Magnus Damm <magnus.damm@gmail.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-sh@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 8/8] sh: clk: Use cpufreq_for_each_valid_entry macro for iteration
Date: Wed, 16 Apr 2014 01:24:55 +0000 [thread overview]
Message-ID: <20140416012454.GA3941@verge.net.au> (raw)
In-Reply-To: <20140416011120.GC8833@verge.net.au>
On Wed, Apr 16, 2014 at 10:11:20AM +0900, Simon Horman wrote:
> On Wed, Apr 16, 2014 at 01:27:04AM +0300, Stratos Karafotis wrote:
> > The cpufreq core now supports the cpufreq_for_each_valid_entry macro
> > helper for iteration over the cpufreq_frequency_table, so use it.
> >
> > It should have no functional changes.
> >
> > Signed-off-by: Stratos Karafotis <stratosk@semaphore.gr>
>
> Thanks, I have queued this up.
I have dropped this patch.
Please let me know if there is a stable branch which
includes cpufreq_frequency_table which I can use as a base to apply
this patch.
Alternatively, I would be happy to Ack this patch and let someone
else pick up this patch, but I'm entirely unclear on who that would be.
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@verge.net.au>
To: Stratos Karafotis <stratosk@semaphore.gr>
Cc: Magnus Damm <magnus.damm@gmail.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-sh@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 8/8] sh: clk: Use cpufreq_for_each_valid_entry macro for iteration
Date: Wed, 16 Apr 2014 10:24:55 +0900 [thread overview]
Message-ID: <20140416012454.GA3941@verge.net.au> (raw)
In-Reply-To: <20140416011120.GC8833@verge.net.au>
On Wed, Apr 16, 2014 at 10:11:20AM +0900, Simon Horman wrote:
> On Wed, Apr 16, 2014 at 01:27:04AM +0300, Stratos Karafotis wrote:
> > The cpufreq core now supports the cpufreq_for_each_valid_entry macro
> > helper for iteration over the cpufreq_frequency_table, so use it.
> >
> > It should have no functional changes.
> >
> > Signed-off-by: Stratos Karafotis <stratosk@semaphore.gr>
>
> Thanks, I have queued this up.
I have dropped this patch.
Please let me know if there is a stable branch which
includes cpufreq_frequency_table which I can use as a base to apply
this patch.
Alternatively, I would be happy to Ack this patch and let someone
else pick up this patch, but I'm entirely unclear on who that would be.
next prev parent reply other threads:[~2014-04-16 1:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 22:27 [PATCH v2 8/8] sh: clk: Use cpufreq_for_each_valid_entry macro for iteration Stratos Karafotis
2014-04-15 22:27 ` Stratos Karafotis
2014-04-16 1:11 ` Simon Horman
2014-04-16 1:11 ` Simon Horman
2014-04-16 1:24 ` Simon Horman [this message]
2014-04-16 1:24 ` Simon Horman
2014-04-16 4:00 ` Viresh Kumar
2014-04-16 4:12 ` Viresh Kumar
2014-04-16 4:13 ` Simon Horman
2014-04-16 4:13 ` Simon Horman
2014-04-16 4:13 ` Simon Horman
2014-04-16 4:13 ` Simon Horman
2014-04-16 7:04 ` Stratos Karafotis
2014-04-16 7:04 ` Stratos Karafotis
2014-04-21 23:02 ` [PATCH v4 " Stratos Karafotis
2014-04-21 23:02 ` Stratos Karafotis
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=20140416012454.GA3941@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=rafael.j.wysocki@intel.com \
--cc=stratosk@semaphore.gr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.