From: Wei Liu <wei.liu@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Wei Liu <wei.liu@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tianyu Lan <Tianyu.Lan@microsoft.com>,
Michael Kelley <mikelley@microsoft.com>
Subject: Re: linux-next: build failure after merge of the hyperv tree
Date: Wed, 1 Apr 2020 18:45:31 +0100 [thread overview]
Message-ID: <20200401174531.by77tjkc2w33fplw@debian> (raw)
In-Reply-To: <20200331172335.2f71021b@canb.auug.org.au>
On Tue, Mar 31, 2020 at 05:23:35PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the hyperv tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: modpost: "panic_on_oops" [drivers/hv/hv_vmbus.ko] undefined!
>
> Caused by commit
>
> a6a5aa4b0179 ("x86/Hyper-V: Report crash data in die() when panic_on_oops is set")
>
> I have reverted that commit for today.
I will remove that patch from hyperv-next. I have been busy with other
things on Monday and Tuesday, so sorry for not paying close attention.
Wei.
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2020-04-01 17:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 6:23 linux-next: build failure after merge of the hyperv tree Stephen Rothwell
2020-04-01 17:45 ` Wei Liu [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-02 7:35 Stephen Rothwell
2023-04-18 17:00 broonie
2023-04-18 17:06 ` Mark Brown
2023-04-18 17:24 ` Wei Liu
2023-04-18 17:31 broonie
2023-04-18 18:34 ` Wei Liu
2023-08-07 4:22 Stephen Rothwell
2023-08-07 4:46 ` Wei Liu
2023-08-08 2:35 ` Dexuan-Linux Cui
2024-03-12 4:18 Stephen Rothwell
2024-03-12 5:25 ` Wei Liu
2025-02-13 3:28 Stephen Rothwell
2025-02-13 22:58 ` Nuno Das Neves
2025-05-06 7:26 Stephen Rothwell
2025-10-20 2:31 Stephen Rothwell
2025-10-20 17:27 ` 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=20200401174531.by77tjkc2w33fplw@debian \
--to=wei.liu@kernel.org \
--cc=Tianyu.Lan@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=sfr@canb.auug.org.au \
/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