cpufreq.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sachin Kamat <sachin.kamat@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Jonghwan Choi <jhbird.choi@samsung.com>
Subject: Re: [PATCH 1/1] cpufreq: exynos: Fix line over 80 characters warning
Date: Thu, 21 Nov 2013 08:28:56 +0530	[thread overview]
Message-ID: <CAK9yfHzCGbqtxVs9WqVLFJ-8v3jLU_B2ZDtWdAFUMEjeFShfwA@mail.gmail.com> (raw)
In-Reply-To: <6133597.QYzlQUus4P@vostro.rjw.lan>

On 21 November 2013 06:24, Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
> On Tuesday, November 19, 2013 10:37:19 AM Sachin Kamat wrote:
>> Silences the checkpatch warning introduced by
>> commit 94aa44090eda ("cpufreq: exynos: Add missing static").
>>
>> Signed-off-by: Sachin Kamat <sachin.kamat@linaro.org>
>> Cc: Jonghwan Choi <jhbird.choi@samsung.com>
>
> I'm not going to apply this and seriously if you care, please modify
> checkpatch.pl to stop emitting that warning.  It is silly and useless in
> my opinion, so I won't take any patches "fixing" it.

Agreed. However, the cpufreq drivers are pretty clean already and
this one just stands out. That was the only reason for doing this.

-- 
With warm regards,
Sachin

      reply	other threads:[~2013-11-21  2:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-19  5:07 [PATCH 1/1] cpufreq: exynos: Fix line over 80 characters warning Sachin Kamat
2013-11-19  5:11 ` Viresh Kumar
2013-11-21  0:54 ` Rafael J. Wysocki
2013-11-21  2:58   ` Sachin Kamat [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=CAK9yfHzCGbqtxVs9WqVLFJ-8v3jLU_B2ZDtWdAFUMEjeFShfwA@mail.gmail.com \
    --to=sachin.kamat@linaro.org \
    --cc=cpufreq@vger.kernel.org \
    --cc=jhbird.choi@samsung.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --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;
as well as URLs for NNTP newsgroup(s).