From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Sean Christopherson <seanjc@google.com>
Cc: James Houghton <jthoughton@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the kvm-x86 tree
Date: Fri, 14 Feb 2025 18:14:01 +1100 [thread overview]
Message-ID: <20250214181401.4e7dd91d@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 339 bytes --]
Hi all,
After merging the kvm-x86 tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
virt/kvm/Kconfig:103:warning: config symbol defined without type
Introduced by commit
5eec660014bf ("KVM: Allow lockless walk of SPTEs when handing aging mmu_notifier event")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-02-14 7:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 7:14 Stephen Rothwell [this message]
2025-02-14 14:55 ` linux-next: build warning after merge of the kvm-x86 tree Sean Christopherson
-- strict thread matches above, loose matches on Subject: below --
2025-06-26 7:10 Stephen Rothwell
2025-06-26 15:56 ` Sean Christopherson
2025-06-27 7:51 ` Stephen Rothwell
2023-01-20 2:09 Stephen Rothwell
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=20250214181401.4e7dd91d@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jthoughton@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=seanjc@google.com \
/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