public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Vorontsov <cbouatmailru@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Len Brown <lenb@kernel.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Durgadoss R <durgadoss.r@intel.com>,
	Jenny TC <jenny.tc@intel.com>
Subject: Re: linux-next: build failure after merge of the final tree (acpi and battery trees related)
Date: Mon, 18 Jun 2012 22:10:32 -0700	[thread overview]
Message-ID: <20120619051032.GB16286@lizard> (raw)
In-Reply-To: <20120619145425.6f825e142856ca808927ca45@canb.auug.org.au>

On Tue, Jun 19, 2012 at 02:54:25PM +1000, Stephen Rothwell wrote:
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig, i386 defconfig) failed like this:
> 
> drivers/power/power_supply_core.c:204:6: error: too few arguments to function 'thermal_zone_device_register'
> 
> Caused by commit a9e7402dd2e4 ("ACPI-Thermal: Make Thermal trip points
> writeable") from the acpi tree interacting with commit 3be330bf8860
> ("power_supply: Register battery as a thermal zone") from the battery
> tree.
> 
> I have added the following patch and will carry it as a merge fix to the
> battery tree:

Thanks for noticing, Stephen! Although, I wonder what would be the
best way to fix this?.. I would happily cherry-pick the ACPI change
into my tree and then re-apply the battery thermal zone support patch,
but ACPI change doesn't apply cleanly on the battery tree. Heh.

Is there thermal zone git tree? Or maybe I would just let ACPI
folks take the battery patch in question?

Thanks,

> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Tue, 19 Jun 2012 14:46:17 +1000
> Subject: [PATCH] ACPI-Thermal: fix for an API change
> 
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
>  drivers/power/power_supply_core.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/power/power_supply_core.c b/drivers/power/power_supply_core.c
> index ff990d2..85689fb 100644
> --- a/drivers/power/power_supply_core.c
> +++ b/drivers/power/power_supply_core.c
> @@ -201,7 +201,7 @@ static int psy_register_thermal(struct power_supply *psy)
>  	for (i = 0; i < psy->num_properties; i++) {
>  		if (psy->properties[i] == POWER_SUPPLY_PROP_TEMP) {
>  			psy->tzd = thermal_zone_device_register(psy->name, 0,
> -					psy, &psy_tzd_ops, 0, 0, 0, 0);
> +					0, psy, &psy_tzd_ops, 0, 0, 0, 0);
>  			if (IS_ERR(psy->tzd))
>  				return PTR_ERR(psy->tzd);
>  			break;
> -- 
> 1.7.10.280.gaa39
> 
> -- 
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au

-- 
Anton Vorontsov
Email: cbouatmailru@gmail.com

  reply	other threads:[~2012-06-19  5:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19  4:54 linux-next: build failure after merge of the final tree (acpi and battery trees related) Stephen Rothwell
2012-06-19  5:10 ` Anton Vorontsov [this message]
2012-06-19  5:37   ` Stephen Rothwell

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=20120619051032.GB16286@lizard \
    --to=cbouatmailru@gmail.com \
    --cc=durgadoss.r@intel.com \
    --cc=jenny.tc@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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