public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel•org>
To: Oliver Upton <oliver.upton@linux•dev>
Cc: kvm@vger•kernel.org, Sebastian Ene <sebastianene@google•com>,
	linux-kernel@vger•kernel.org, aneesh.kumar@kernel•org,
	kvmarm@lists•linux.dev, Nicholas Piggin <npiggin@gmail•com>,
	Sean Christopherson <seanjc@google•com>,
	naveen.n.rao@linux•ibm.com, Paolo Bonzini <pbonzini@redhat•com>,
	linuxppc-dev@lists•ozlabs.org
Subject: Re: [PATCH] KVM: Get rid of return value from kvm_arch_create_vm_debugfs()
Date: Fri, 16 Feb 2024 17:13:10 +0000	[thread overview]
Message-ID: <86h6i849jt.wl-maz@kernel.org> (raw)
In-Reply-To: <20240216155941.2029458-1-oliver.upton@linux.dev>

On Fri, 16 Feb 2024 15:59:41 +0000,
Oliver Upton <oliver.upton@linux•dev> 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.
> 
> Signed-off-by: Oliver Upton <oliver.upton@linux•dev>

Acked-by: Marc Zyngier <maz@kernel•org>

	M.

-- 
Without deviation from the norm, progress is not possible.

  reply	other threads:[~2024-02-16 17:14 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 [this message]
2024-02-23 15:31 ` Paolo Bonzini
2024-02-23 21:51 ` Oliver Upton

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=86h6i849jt.wl-maz@kernel.org \
    --to=maz@kernel$(echo .)org \
    --cc=aneesh.kumar@kernel$(echo .)org \
    --cc=kvm@vger$(echo .)kernel.org \
    --cc=kvmarm@lists$(echo .)linux.dev \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=naveen.n.rao@linux$(echo .)ibm.com \
    --cc=npiggin@gmail$(echo .)com \
    --cc=oliver.upton@linux$(echo .)dev \
    --cc=pbonzini@redhat$(echo .)com \
    --cc=seanjc@google$(echo .)com \
    --cc=sebastianene@google$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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