public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Valentin <edubezval@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Javi Merino <javi.merino@arm.com>
Subject: Re: linux-next: build failure after merge of the thermal-soc tree
Date: Wed, 4 Mar 2015 15:01:52 -0400	[thread overview]
Message-ID: <20150304190150.GA3427@developer.amazonguestwifi.org> (raw)
In-Reply-To: <20150304180636.78c66f79@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

Hi Stephen,

On Wed, Mar 04, 2015 at 06:06:36PM +1100, Stephen Rothwell wrote:
> Hi Eduardo,
> 
> After merging the thermal-soc tree, today's linux-next build (arm
> cm_x2xx_defconfig (at least)) failed like this:
> 
> include/linux/thermal.h:408:38: error: parameter name omitted
> include/linux/thermal.h:413:1: error: expected identifier or '(' before '{' token
> 
> Caused by commit ddd4dd8ddf78 ("thermal: extend the cooling device API
> to include power information").
> 

Thanks for pointing it out. Javi has already provided a fix and I
already added in my -linus branch. I will appear in your next linux-next
build.

BR,

Eduardo Valentin

> -- 
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au



[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-03-04 19:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04  7:06 linux-next: build failure after merge of the thermal-soc tree Stephen Rothwell
2015-03-04 19:01 ` Eduardo Valentin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-11-05  5:01 Stephen Rothwell
2015-11-05 10:22 ` Caesar Wang
2015-11-09 19:17   ` Eduardo Valentin
2015-12-31  1:53 Stephen Rothwell
2015-12-31 17:01 ` Srinivas Pandruvada
2019-05-13  1:02 Stephen Rothwell
2019-05-13 15:57 ` Guenter Roeck

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=20150304190150.GA3427@developer.amazonguestwifi.org \
    --to=edubezval@gmail.com \
    --cc=javi.merino@arm.com \
    --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