From: Zhang Rui <rui.zhang@intel•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Daniel Lezcano <daniel.lezcano@linaro•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Andres Freund <andres@anarazel•de>
Subject: Re: linux-next: build failure after merge of the thermal tree
Date: Mon, 23 Mar 2020 14:59:24 +0800 [thread overview]
Message-ID: <9698a9f2c49e3ca286b946eeb7de3399c406ea5e.camel@intel.com> (raw)
In-Reply-To: <20200323110852.1f08e4f1@canb.auug.org.au>
On Mon, 2020-03-23 at 11:08 +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the thermal tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/thermal/intel/intel_pch_thermal.c:306:2: error: expected '}'
> before '[' token
> 306 | [board_lwb] = {
> | ^
> drivers/thermal/intel/intel_pch_thermal.c:285:18: note: to match this
> '{'
> 285 | } board_info[] = {
> | ^
>
> Caused by commit
>
> 16cd95bab00f ("thermal: intel_pch_thermal: Add PCI ids for
> Lewisburg PCH.")
>
> I have used the thermal tree from next-20200320 for today.
>
Bug has been fixed.
BTW, I think you can remove Eduardo from this loop, because he is not
working as the thermal maintainer right now.
thanks,
rui
next prev parent reply other threads:[~2020-03-23 6:59 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 0:08 linux-next: build failure after merge of the thermal tree Stephen Rothwell
2020-03-23 6:59 ` Zhang Rui [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-27 12:56 Mark Brown
2026-05-27 19:50 ` Ronald Claveau
2026-05-29 14:57 ` Mark Brown
2023-12-18 23:34 Stephen Rothwell
2023-12-19 2:10 ` Fabio Estevam
2023-12-19 17:59 ` Daniel Lezcano
2023-12-21 1:17 ` Stephen Rothwell
2023-12-21 15:23 ` Fabio Estevam
2023-01-24 23:02 Stephen Rothwell
2023-01-16 0:08 Stephen Rothwell
2023-01-04 23:46 Stephen Rothwell
2023-01-05 9:38 ` Daniel Lezcano
2022-08-03 13:05 broonie
2022-08-03 13:24 ` Daniel Lezcano
2022-08-01 22:35 broonie
2022-08-02 15:04 ` Mark Brown
2022-08-02 15:19 ` Daniel Lezcano
2020-12-15 1:58 Stephen Rothwell
2020-03-03 6:07 Stephen Rothwell
2020-03-03 7:55 ` Daniel Lezcano
2020-03-03 7:57 ` Anson Huang
2019-12-11 22:50 Stephen Rothwell
2019-12-12 22:14 ` Stephen Rothwell
2019-12-13 1:03 ` Daniel Lezcano
2019-12-20 0:04 ` Stephen Rothwell
2019-12-20 8:25 ` Daniel Lezcano
2018-12-07 1:24 Stephen Rothwell
2018-12-07 6:57 ` Amit Kucheria
2018-06-08 0:51 Stephen Rothwell
2018-06-08 1:07 ` Stephen Rothwell
2014-12-09 2:17 Stephen Rothwell
2014-12-09 2:31 ` Aaron Lu
2014-12-09 2:32 ` Zhang Rui
2014-10-16 1:53 Stephen Rothwell
2014-10-10 1:14 Stephen Rothwell
2014-10-10 8:19 ` Zhang Rui
2012-10-08 0:02 Stephen Rothwell
2012-10-08 2:14 ` Zhang, Rui
2012-10-09 2:11 ` Fengguang Wu
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=9698a9f2c49e3ca286b946eeb7de3399c406ea5e.camel@intel.com \
--to=rui.zhang@intel$(echo .)com \
--cc=andres@anarazel$(echo .)de \
--cc=daniel.lezcano@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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