public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: broonie@kernel.org
To: Long Li <longli@microsoft.com>,
	Michael Kelley <mikelley@microsoft.com>,
	Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
	"K. Y. Srinivasan" <kys@microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	linux-hyperv@vger.kernel.org
Subject: linux-next: build failure after merge of the hyperv tree
Date: Tue, 18 Apr 2023 18:31:57 +0100	[thread overview]
Message-ID: <20230418173157.92827-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/drivers/hv/connection.c: In function 'vmbus_connect':
/tmp/next/build/drivers/hv/connection.c:228:53: error: implicit
declaration of function 'hv_alloc_hyperv_page'; did you mean 'hv_free_hyperv_page'? [-Werror=implicit-function-declaration]
  228 |         vmbus_connection.monitor_pages[0] = (void *)hv_alloc_hyperv_page();
      |                                                     ^~~~~~~~~~~~~~~~~~~~
      |                                                     hv_free_hyperv_page
/tmp/next/build/drivers/hv/connection.c:228:45: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]
  228 |         vmbus_connection.monitor_pages[0] = (void *)hv_alloc_hyperv_page();
      |                                             ^
/tmp/next/build/drivers/hv/connection.c:229:45: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]
  229 |         vmbus_connection.monitor_pages[1] = (void *)hv_alloc_hyperv_page();
      |                                             ^
cc1: all warnings being treated as errors

Caused by commit

  4dbdcfe1c5db80edca ("Drivers: hv: move panic report code from vmbus to hv early init code")

I will use the hyperv tree from yesterday instead.

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

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18 17:31 broonie [this message]
2023-04-18 18:34 ` linux-next: build failure after merge of the hyperv tree 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:00 broonie
2023-04-18 17:06 ` Mark Brown
2023-04-18 17:24   ` 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=20230418173157.92827-1-broonie@kernel.org \
    --to=broonie@kernel.org \
    --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=longli@microsoft.com \
    --cc=mikelley@microsoft.com \
    --cc=wei.liu@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