From: "Wysocki, Rafael J" <rafael.j.wysocki@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>,
<linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: linux-next: build failure after merge of the pm tree
Date: Fri, 14 Jul 2023 20:19:53 +0200 [thread overview]
Message-ID: <71f62e49-3f2f-a8bf-2347-061902d39f7e@intel.com> (raw)
In-Reply-To: <20230714110051.4575ffbe@canb.auug.org.au>
Daniel,
On 7/14/2023 3:00 AM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the pm tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> In file included from drivers/thermal/tegra/soctherm.c:36:
> drivers/thermal/tegra/../thermal_core.h:18:2: error: #warning This header can only be included by the thermal core code [-Werror-cpp]
> 18 | #warning This header can only be included by the thermal core code
> | ^~~~~~~
>
> Introduced by commit
>
> bc1bb350b534 ("thermal/core: Hardening the self-encapsulation")
I'll drop this patch. I think that the rest of the series doesn't
really depend on it.
> I have used the pm tree from next-20230713 for today.
Thanks!
next parent reply other threads:[~2023-07-14 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230714110051.4575ffbe@canb.auug.org.au>
2023-07-14 18:19 ` Wysocki, Rafael J [this message]
2023-07-14 18:50 ` linux-next: build failure after merge of the pm tree Rafael J. Wysocki
[not found] <20220428110030.7090a45b@canb.auug.org.au>
2022-04-28 8:56 ` Zhang Rui
2022-04-28 12:32 ` Rafael J. Wysocki
[not found] <20220104111551.7f26e893@canb.auug.org.au>
[not found] ` <d485fb62-b576-f9b6-13bc-709a2c409240@gmail.com>
[not found] ` <20220104190220.45c8e0cf@canb.auug.org.au>
2022-01-04 14:43 ` Heiner Kallweit
2022-01-04 14:57 ` Rafael J. Wysocki
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=71f62e49-3f2f-a8bf-2347-061902d39f7e@intel.com \
--to=rafael.j.wysocki@intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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