linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Zhang Rui <rui.zhang@intel.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: build failure after merge of the thermal tree
Date: Thu, 16 Oct 2014 12:53:21 +1100	[thread overview]
Message-ID: <20141016125321.20509c53@canb.auug.org.au> (raw)

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

Hi Zhang,

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

drivers/thermal/thermal_core.c:1183:1: error: redefinition of 'thermal_cooling_device_register'
 thermal_cooling_device_register(char *type, void *devdata,
 ^
In file included from drivers/thermal/thermal_core.c:34:0:
include/linux/thermal.h:345:46: note: previous definition of 'thermal_cooling_device_register' was here
 static inline struct thermal_cooling_device *thermal_cooling_device_register(
                                              ^
drivers/thermal/thermal_core.c:1221:6: error: redefinition of 'thermal_cooling_device_unregister'
 void thermal_cooling_device_unregister(struct thermal_cooling_device *cdev)
      ^
In file included from drivers/thermal/thermal_core.c:34:0:
include/linux/thermal.h:351:20: note: previous definition of 'thermal_cooling_device_unregister' was here
 static inline void thermal_cooling_device_unregister(struct thermal_cooling_device *cdev)
                    ^

Caused by commit 571ed5a8177a ("Thermal: int340x thermal: fix a Kconfig
dependency error").

I have reverted that commit for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2014-10-16  1:53 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16  1:53 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-18 23:34 linux-next: build failure after merge of the thermal tree 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-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-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=20141016125321.20509c53@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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).