public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: stratosk@semaphore•gr (Stratos Karafotis)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 08/20] cpufreq: exynos5440: Use cpufreq_for_each_entry macro for iteration
Date: Tue, 15 Apr 2014 14:02:26 +0300	[thread overview]
Message-ID: <534D11C2.3080206@semaphore.gr> (raw)
In-Reply-To: <CAKohpokfsR3soykZbtH4-L=4TC6Oab=jyzUr=W-EfkRFfefRDQ@mail.gmail.com>

On 15/04/2014 08:44 ??, Viresh Kumar wrote:
> On 15 April 2014 02:39, Stratos Karafotis <stratosk@semaphore•gr> wrote:
> 
>> diff --git a/drivers/cpufreq/exynos5440-cpufreq.c b/drivers/cpufreq/exynos5440-cpufreq.c
> 
>>  static void exynos_enable_dvfs(unsigned int cur_frequency)
>>  {
>> -       unsigned int tmp, i, cpu;
>> +       unsigned int tmp, cpu;
>>         struct cpufreq_frequency_table *freq_table = dvfs_info->freq_table;
>> +       struct cpufreq_frequency_table *pos;
> 
> Merge above two.
> 

Then the line will be 82 characters long.
Do you mind to keep it as is?


Stratos

      reply	other threads:[~2014-04-15 11:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 21:09 [PATCH 08/20] cpufreq: exynos5440: Use cpufreq_for_each_entry macro for iteration Stratos Karafotis
2014-04-15  5:44 ` Viresh Kumar
2014-04-15 11:02   ` Stratos Karafotis [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=534D11C2.3080206@semaphore.gr \
    --to=stratosk@semaphore$(echo .)gr \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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