From: Paolo Bonzini <pbonzini@redhat.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Anup Patel <anup.patel@wdc.com>,
Atish Patra <atish.patra@wdc.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
linux-riscv@lists.infradead.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: do not select non-existing config ANON_INODES
Date: Fri, 22 Oct 2021 11:53:48 +0200 [thread overview]
Message-ID: <5c27a2ff-b7a2-99d8-bdc4-7f2b20092500@redhat.com> (raw)
In-Reply-To: <20211022061514.25946-1-lukas.bulwahn@gmail.com>
On 22/10/21 08:15, Lukas Bulwahn wrote:
> Commit 99cdc6c18c2d ("RISC-V: Add initial skeletal KVM support") selects
> the config ANON_INODES in config KVM, but the config ANON_INODES is removed
> since commit 5dd50aaeb185 ("Make anon_inodes unconditional") in 2018.
>
> Hence, ./scripts/checkkconfigsymbols.py warns on non-existing symbols:
>
> ANON_INODES
> Referencing files: arch/riscv/kvm/Kconfig
>
> Remove selecting the non-existing config ANON_INODES.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> arch/riscv/kvm/Kconfig | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/riscv/kvm/Kconfig b/arch/riscv/kvm/Kconfig
> index a712bb910cda..f5a342fa1b1d 100644
> --- a/arch/riscv/kvm/Kconfig
> +++ b/arch/riscv/kvm/Kconfig
> @@ -22,7 +22,6 @@ config KVM
> depends on RISCV_SBI && MMU
> select MMU_NOTIFIER
> select PREEMPT_NOTIFIERS
> - select ANON_INODES
> select KVM_MMIO
> select KVM_GENERIC_DIRTYLOG_READ_PROTECT
> select HAVE_KVM_VCPU_ASYNC_IOCTL
>
Queued, thanks.
Paolo
next prev parent reply other threads:[~2021-10-22 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 6:15 [PATCH] riscv: do not select non-existing config ANON_INODES Lukas Bulwahn
2021-10-22 9:53 ` Paolo Bonzini [this message]
2021-10-22 11:55 ` Anup Patel
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=5c27a2ff-b7a2-99d8-bdc4-7f2b20092500@redhat.com \
--to=pbonzini@redhat.com \
--cc=anup.patel@wdc.com \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@wdc.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lukas.bulwahn@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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