linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <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>,
	linux-hyperv@vger.kernel.org,
	"K. Y. Srinivasan" <kys@microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Dexuan Cui <decui@microsoft.com>
Subject: Re: linux-next: build failure after merge of the hyperv tree
Date: Tue, 18 Apr 2023 18:06:58 +0100	[thread overview]
Message-ID: <e8780a61-96e9-4050-b0d5-8e6be43e2e27@sirena.org.uk> (raw)
In-Reply-To: <20230418170021.90280-1-broonie@kernel.org>

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

On Tue, Apr 18, 2023 at 06:00:21PM +0100, broonie@kernel.org wrote:
> Hi all,
> 
> After merging the hyperv tree, today's linux-next build (x86 allmodconfig)
> failed like this:

Adding more Hyper-V CCs, sorry the capitialisation in MAINTAINERS
confused my search.

> 
> /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.

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

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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18 17:00 linux-next: build failure after merge of the hyperv tree broonie
2023-04-18 17:06 ` Mark Brown [this message]
2023-04-18 17:24   ` Wei Liu
  -- strict thread matches above, loose matches on Subject: below --
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=e8780a61-96e9-4050-b0d5-8e6be43e2e27@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=bp@alien8.de \
    --cc=decui@microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --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 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).