From: Oliver Upton <oliver.upton@linux.dev>
To: Oliver Upton <oliver.upton@linux.dev>, kvm@vger.kernel.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
kvmarm@lists.linux.dev, aneesh.kumar@kernel.org,
Sean Christopherson <seanjc@google.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>,
Marc Zyngier <maz@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Sebastian Ene <sebastianene@google.com>,
naveen.n.rao@linux.ibm.com,
Christophe Leroy <christophe.leroy@csgroup.eu>
Subject: Re: [PATCH] KVM: Get rid of return value from kvm_arch_create_vm_debugfs()
Date: Fri, 23 Feb 2024 21:51:12 +0000 [thread overview]
Message-ID: <170872506304.206263.3199862434632781431.b4-ty@linux.dev> (raw)
In-Reply-To: <20240216155941.2029458-1-oliver.upton@linux.dev>
On Fri, 16 Feb 2024 15:59:41 +0000, Oliver Upton wrote:
> The general expectation with debugfs is that any initialization failure
> is nonfatal. Nevertheless, kvm_arch_create_vm_debugfs() allows
> implementations to return an error and kvm_create_vm_debugfs() allows
> that to fail VM creation.
>
> Change to a void return to discourage architectures from making debugfs
> failures fatal for the VM. Seems like everyone already had the right
> idea, as all implementations already return 0 unconditionally.
>
> [...]
Applied to kvmarm/next, thanks!
[1/1] KVM: Get rid of return value from kvm_arch_create_vm_debugfs()
https://git.kernel.org/kvmarm/kvmarm/c/284851ee5cae
--
Best,
Oliver
prev parent reply other threads:[~2024-02-23 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 15:59 [PATCH] KVM: Get rid of return value from kvm_arch_create_vm_debugfs() Oliver Upton
2024-02-16 17:13 ` Marc Zyngier
2024-02-23 15:31 ` Paolo Bonzini
2024-02-23 21:51 ` Oliver Upton [this message]
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=170872506304.206263.3199862434632781431.b4-ty@linux.dev \
--to=oliver.upton@linux.dev \
--cc=aneesh.kumar@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maz@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=sebastianene@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).