linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	linux-pm@vger.kernel.org,
	Lists linaro-dev <linaro-dev@lists.linaro.org>
Subject: Re: drivers/cpufreq/cpufreq_governor.c:46:53: sparse: incorrect type in argument 2 (different modifiers)
Date: Tue, 23 Oct 2012 15:41:19 +0800	[thread overview]
Message-ID: <20121023074119.GA921@localhost> (raw)
In-Reply-To: <CAKohpo=PF-MkG8KDRWSfoBXkK102r7WwToQ01UmfetvarRyK3w@mail.gmail.com>

Hi Viresh,

On Tue, Oct 23, 2012 at 10:55:51AM +0530, Viresh Kumar wrote:
> Hi Fengguang,
> 
> Thanks for your mail. Few things i learnt from it:
> - Rafael has already applied my patches :)
> - I haven't used sparse in my life till this point. Now i know how to use it.

Good to know that! :-)

> On 23 October 2012 10:21, Fengguang Wu <fengguang.wu@intel.com> wrote:
> > Hi viresh,
> >
> > FYI, there are new sparse warnings show up in
> 
> Actually these aren't new warnings, but old. Because some part is moved from
> one file to another, that's why your script shows them as new warnings.

You are right, the build system is actually catching new "error
messages" strictly speaking.

> Anyway, i don't hesitate in fixing them.

Thanks and appreciated!

Thanks,
Fengguang

  reply	other threads:[~2012-10-23  7:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23  4:51 drivers/cpufreq/cpufreq_governor.c:46:53: sparse: incorrect type in argument 2 (different modifiers) Fengguang Wu
2012-10-23  5:25 ` Viresh Kumar
2012-10-23  7:41   ` Fengguang Wu [this message]
2012-10-24  0:33   ` Rafael J. Wysocki
2012-10-24  6:35     ` Viresh Kumar

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=20121023074119.GA921@localhost \
    --to=fengguang.wu@intel.com \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.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;
as well as URLs for NNTP newsgroup(s).