archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <>
To: Daniel Lezcano <>
Cc: "Zhang Rui" <>,
	"Linux PM mailing list" <>,
	"Linux Kernel Mailing List" <>,
	"Chunyan Zhang" <>,
	"Srinivas Pandruvada" <>,
	"Rajeshwari Ravindra Kamble" <>,
	"Yang Yingliang" <>,
	"Niklas Söderlund" <>,
	"Krzysztof Kozlowski" <>,
	"Dmitry Osipenko" <>,
	"Ezequiel Garcia" <>,
	"Bjorn Andersson" <>,
	"Andy Shevchenko" <>,
	"Yangtao Li" <>,
	"Finley Xiao" <>
Subject: Re: [GIT PULL] thermal for v5.14-rc1
Date: Sat, 3 Jul 2021 12:34:05 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sat, Jul 3, 2021 at 9:17 AM Daniel Lezcano <> wrote:
> ssh://
> tags/thermal-v5.14-rc1

This does not build for me. And I suspect it never built in linux-next either.

I get

  ERROR: modpost: "tegra_fuse_readl"
[drivers/thermal/tegra/tegra30-tsensor.ko] undefined!
  ERROR: modpost: "tegra_fuse_readl"
[drivers/thermal/tegra/tegra-soctherm.ko] undefined!
  make[1]: *** [scripts/Makefile.modpost:150: modules-only.symvers] Error 1
  make[1]: *** Deleting file 'modules-only.symvers'
  make: *** [Makefile:1762: modules] Error 2

and I think it's due to that commit 1f9c5936b10c
("thermal/drivers/tegra: Correct compile-testing of drivers") which
quite sensibly tries to extend build coverage for the tegra thermal
drivers, but that build coverage doesn't actually *work* outside the
tegra world.

That commit says "All Tegra thermal drivers support compile-testing",
but clearly they stumble at the last hurdle.

I made the decision to just unpull this, not because I couldn't fix
it, but because if it was this untested, I don't want to worry about
all the *other* code in there too.


  reply	other threads:[~2021-07-03 19:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03 16:17 [GIT PULL] thermal for v5.14-rc1 Daniel Lezcano
2021-07-03 19:34 ` Linus Torvalds [this message]
2021-07-03 19:56   ` Dmitry Osipenko
2021-07-04  9:51     ` Daniel Lezcano
2021-07-04 12:04       ` Dmitry Osipenko
2021-07-04 13:19         ` Daniel Lezcano
2021-07-04 13:28           ` Dmitry Osipenko

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).