All of lore.kernel.org
 help / color / mirror / Atom feed
From: broonie@kernel.org
To: Tianyu Lan <tiala@microsoft.com>,
	Saurabh Sengar <ssengar@linux.microsoft.com>,
	Wei Liu <wei.liu@kernel.org>,
	Michael Kelley <mikelley@microsoft.com>,
	Borislav Petkov <bp@alien8.de>,
	x86@kernel.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the hyperv tree
Date: Tue, 18 Apr 2023 18:00:21 +0100	[thread overview]
Message-ID: <20230418170021.90280-1-broonie@kernel.org> (raw)

Hi all,

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

/tmp/next/build/arch/x86/kernel/x86_init.c:36:12: error: static declaration of 'set_rtc_noop' follows non-static declaration
   36 | static int set_rtc_noop(const struct timespec64 *now) { return -EINVAL; }
      |            ^~~~~~~~~~~~
In file included from /tmp/next/build/arch/x86/include/asm/mpspec.h:7,
                 from /tmp/next/build/arch/x86/include/asm/topology.h:38,
                 from /tmp/next/build/include/linux/topology.h:36,
                 from /tmp/next/build/include/linux/gfp.h:8,
                 from /tmp/next/build/include/linux/xarray.h:15,
                 from /tmp/next/build/include/linux/radix-tree.h:21,
                 from /tmp/next/build/include/linux/idr.h:15,
                 from /tmp/next/build/include/linux/kernfs.h:12,
                 from /tmp/next/build/include/linux/sysfs.h:16,
                 from /tmp/next/build/include/linux/kobject.h:20,
                 from /tmp/next/build/include/linux/pci.h:35,
                 from /tmp/next/build/arch/x86/kernel/x86_init.c:9:
/tmp/next/build/arch/x86/include/asm/x86_init.h:333:12: note: previous declaration of 'set_rtc_noop' with type 'int(const struct timespec64 *)'
  333 | extern int set_rtc_noop(const struct timespec64 *now);
      |            ^~~~~~~~~~~~
/tmp/next/build/arch/x86/kernel/x86_init.c:37:13: error: static declaration of 'get_rtc_noop' follows non-static declaration
   37 | static void get_rtc_noop(struct timespec64 *now) { }
      |             ^~~~~~~~~~~~
In file included from /tmp/next/build/arch/x86/include/asm/mpspec.h:7,
                 from /tmp/next/build/arch/x86/include/asm/topology.h:38,
                 from /tmp/next/build/include/linux/topology.h:36,
                 from /tmp/next/build/include/linux/gfp.h:8,
                 from /tmp/next/build/include/linux/xarray.h:15,
                 from /tmp/next/build/include/linux/radix-tree.h:21,
                 from /tmp/next/build/include/linux/idr.h:15,
                 from /tmp/next/build/include/linux/kernfs.h:12,
                 from /tmp/next/build/include/linux/sysfs.h:16,
                 from /tmp/next/build/include/linux/kobject.h:20,
                 from /tmp/next/build/include/linux/pci.h:35,
                 from /tmp/next/build/arch/x86/kernel/x86_init.c:9:
/tmp/next/build/arch/x86/include/asm/x86_init.h:334:13: note: previous declaration of 'get_rtc_noop' with type 'void(struct timespec64 *)'
  334 | extern void get_rtc_noop(struct timespec64 *now);
      |             ^~~~~~~~~~~~

Caused by commit

  25dcc7316ef7def25c ("x86/init: Make get/set_rtc_noop() public")

I will use the hyperv tree from yesterday instead.

             reply	other threads:[~2023-04-18 17:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18 17:00 broonie [this message]
2023-04-18 17:06 ` linux-next: build failure after merge of the hyperv tree Mark Brown
2023-04-18 17:24   ` Wei Liu
  -- strict thread matches above, loose matches on Subject: below --
2025-10-20  2:31 Stephen Rothwell
2025-10-20 17:27 ` Wei Liu
2025-05-06  7:26 Stephen Rothwell
2025-02-13  3:28 Stephen Rothwell
2025-02-13 22:58 ` Nuno Das Neves
2024-03-12  4:18 Stephen Rothwell
2024-03-12  5:25 ` Wei Liu
2023-08-07  4:22 Stephen Rothwell
2023-08-07  4:46 ` Wei Liu
2023-08-08  2:35   ` Dexuan-Linux Cui
2023-04-18 17:31 broonie
2023-04-18 18:34 ` Wei Liu
2020-06-02  7:35 Stephen Rothwell
2020-03-31  6:23 Stephen Rothwell
2020-04-01 17:45 ` Wei Liu

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=20230418170021.90280-1-broonie@kernel.org \
    --to=broonie@kernel.org \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mikelley@microsoft.com \
    --cc=ssengar@linux.microsoft.com \
    --cc=tiala@microsoft.com \
    --cc=wei.liu@kernel.org \
    --cc=x86@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.