linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: broonie@kernel.org
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
	Zhang Rui <rui.zhang@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Amit Kucheria <amitk@kernel.org>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	linux-samsung-soc@vger.kernel.org
Subject: linux-next: build failure after merge of the thermal tree
Date: Mon,  1 Aug 2022 23:35:09 +0100	[thread overview]
Message-ID: <20220801223509.3613888-1-broonie@kernel.org> (raw)

Hi all,

After merging the thermal tree, today's linux-next build (x86
allmodconfig) failed like this:

/tmp/next/build/drivers/thermal/samsung/exynos_tmu.c:753:44: warning: 'struct thermal_zone' declared inside parameter list will not be visible outside of this definition or declaration
  753 | static int exynos_tmu_set_emulation(struct thermal_zone *tz, int temp)
      |                                            ^~~~~~~~~~~~
/tmp/next/build/drivers/thermal/samsung/exynos_tmu.c:1002:19: error: initialization of 'int (*)(struct thermal_zone_device *, int)' from incompatible pointer type 'int (*)(struct thermal_zone *, int)' [-Werror=incompatible-pointer-types]
 1002 |  .set_emul_temp = exynos_tmu_set_emulation,
      |                   ^~~~~~~~~~~~~~~~~~~~~~~~
/tmp/next/build/drivers/thermal/samsung/exynos_tmu.c:1002:19: note: (near initialization for 'exynos_sensor_ops.set_emul_temp')
cc1: some warnings being treated as errors

Caused by commit

  a5e9a144258bf898 ("thermal/drivers/samsung: Switch to new of thermal API")

which looks like it missed some conversions.

I'll figure out how to handle this tomorrow since I don't expect to
release today, I'm just droping the tree for now.

             reply	other threads:[~2022-08-01 22:36 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 22:35 broonie [this message]
2022-08-02 15:04 ` linux-next: build failure after merge of the thermal tree Mark Brown
2022-08-02 15:19   ` Daniel Lezcano
  -- strict thread matches above, loose matches on Subject: below --
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
2020-12-15  1:58 Stephen Rothwell
2020-03-23  0:08 Stephen Rothwell
2020-03-23  6:59 ` Zhang Rui
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=20220801223509.3613888-1-broonie@kernel.org \
    --to=broonie@kernel.org \
    --cc=amitk@kernel.org \
    --cc=bzolnier@gmail.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).