All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jinke Fan <fanjinke@hygon.cn>
Subject: linux-next: build failure after merge of the rtc tree
Date: Fri, 4 Oct 2019 14:37:31 +1000	[thread overview]
Message-ID: <20191004143731.30f97c7f@canb.auug.org.au> (raw)

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

Hi all,

After merging the rtc tree, today's linux-next build (powerpc
allyesconfig) failed like this:

drivers/rtc/rtc-mc146818-lib.c: In function 'mc146818_set_time':
drivers/rtc/rtc-mc146818-lib.c:176:6: error: 'boot_cpu_data' undeclared (first use in this function); did you mean 'bootmem_data'?
  176 |  if (boot_cpu_data.x86_vendor == X86_VENDOR_AMD ||
      |      ^~~~~~~~~~~~~
      |      bootmem_data
drivers/rtc/rtc-mc146818-lib.c:176:6: note: each undeclared identifier is reported only once for each function it appears in
drivers/rtc/rtc-mc146818-lib.c:176:34: error: 'X86_VENDOR_AMD' undeclared (first use in this function); did you mean 'X86_VENDOR_ANY'?
  176 |  if (boot_cpu_data.x86_vendor == X86_VENDOR_AMD ||
      |                                  ^~~~~~~~~~~~~~
      |                                  X86_VENDOR_ANY
drivers/rtc/rtc-mc146818-lib.c:177:34: error: 'X86_VENDOR_HYGON' undeclared (first use in this function); did you mean 'X86_VENDOR_ANY'?
  177 |      boot_cpu_data.x86_vendor == X86_VENDOR_HYGON)
      |                                  ^~~~~~~~~~~~~~~~
      |                                  X86_VENDOR_ANY

Caused by commit

  1e2c8aadedbe ("rtc: cmos: fix the AltCentury value on AMD/Hygon platform")

This driver file is built for several different architecture, but
the added code is X86 specific :-(

I have reverted that commit for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-10-04  4:37 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-04  4:37 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-16  4:15 linux-next: build failure after merge of the rtc tree Stephen Rothwell
2023-10-16  4:34 ` Alexandre Belloni
2023-10-16  7:11 ` Uwe Kleine-König
2021-09-27  3:10 Stephen Rothwell
2021-09-27  7:16 ` Romain Perier
2021-08-10  5:54 Stephen Rothwell
2020-03-16  5:15 Stephen Rothwell
2020-03-16  6:58 ` Ran Bi
2020-03-16 10:31   ` Alexandre Belloni
2019-02-11  5:24 Stephen Rothwell
2019-02-08  5:55 Stephen Rothwell
2017-05-31  4:33 Stephen Rothwell
2017-05-31  5:45 ` Heiner Kallweit
2017-05-31  7:19   ` Alexandre Belloni
2017-04-10  6:04 Stephen Rothwell
2017-04-10  7:45 ` Hans de Goede
2017-04-11  0:22   ` Stephen Rothwell
2017-04-11  5:55     ` Alexandre Belloni
2017-04-11  7:52       ` Stephen Rothwell
2017-04-14 10:09         ` Alexandre Belloni
2017-04-14 16:33           ` Stephen Rothwell
2016-11-08  6:41 Stephen Rothwell
2016-11-08 22:21 ` Alexandre Belloni
2015-12-17  5:03 Stephen Rothwell
2015-12-17 11:21 ` Alexandre Belloni
2015-12-17 11:21   ` Alexandre Belloni
2015-12-18 15:30   ` Sasha Levin
2015-12-18 16:43     ` Alexandre Belloni
2015-12-22 19:27       ` Alexandre Belloni

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=20191004143731.30f97c7f@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=alexandre.belloni@bootlin.com \
    --cc=fanjinke@hygon.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.