linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
To: "arnd@arndb.de" <arnd@arndb.de>, "rjw@rjwysocki.net" <rjw@rjwysocki.net>
Cc: "lenb@kernel.org" <lenb@kernel.org>,
	"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
	"Gasparini, Stephane" <stephane.gasparini@intel.com>,
	"philippe.longepe@linux.intel.com"
	<philippe.longepe@linux.intel.com>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpufreq: intel_pstate: fix intel_pstate_use_acpi_profile helper
Date: Mon, 14 Nov 2016 17:53:02 +0000	[thread overview]
Message-ID: <1479145979.6544.19.camel@intel.com> (raw)
In-Reply-To: <1479143663.6544.11.camel@linux.intel.com>

On Mon, 2016-11-14 at 09:14 -0800, Srinivas Pandruvada wrote:
> On Mon, 2016-11-14 at 17:41 +0100, Arnd Bergmann wrote:
> > 
> > The newly added function uses two different prototypes depending
> > on configuration, and one of them does not match the caller:
> > 
> > drivers/cpufreq/intel_pstate.c: In function ‘copy_cpu_funcs’:
> > drivers/cpufreq/intel_pstate.c:1798:2: error: too few arguments to
> > function ‘intel_pstate_use_acpi_profile’
> > 
> > This changes it to look like the other one.
> Sorry about that.

Since this is a compile issue for x86 non ACPI systems, which will be a
problem for git bisect, it is better to resubmit my patch with the fix.

Thanks,
Srinivas

      reply	other threads:[~2016-11-14 17:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14 16:41 [PATCH] cpufreq: intel_pstate: fix intel_pstate_use_acpi_profile helper Arnd Bergmann
2016-11-14 17:14 ` Srinivas Pandruvada
2016-11-14 17:53   ` Pandruvada, Srinivas [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=1479145979.6544.19.camel@intel.com \
    --to=srinivas.pandruvada@intel.com \
    --cc=arnd@arndb.de \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=philippe.longepe@linux.intel.com \
    --cc=rjw@rjwysocki.net \
    --cc=stephane.gasparini@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).