All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger@xenproject.org>
To: Jan Beulich <jbeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Teddy Astie <teddy.astie@vates.tech>
Subject: Re: [PATCH v2 4/5] x86/vPCI: make better use of "pdev" in vpci_msix_arch_print()
Date: Wed, 28 Oct 2026 15:38:38 +0100	[thread overview]
Message-ID: <auII7rNEJN-xvkql@Mac.lan> (raw)
In-Reply-To: <b21db453-c2ad-4321-8f8f-76d801dfe998@suse.com>

On Wed, Sep 30, 2026 at 01:43:34PM +0200, Jan Beulich wrote:
> Move the declaration to function scope, so that not only the (so far)
> immediately following spin_unlock() can make use of it, but also the
> assertions at the top. Also add const, as the pdev itself isn't supposed
> to be altered here.
> 
> Signed-off-by: Jan Beulich <jbeulich@suse.com>

Acked-by: Roger Pau Monné <roger@xenproject.org>

Thanks, Roger.


  reply	other threads:[~2026-10-28 14:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30 11:40 [PATCH v2 0/5] x86: pass-through / {,v}PCI locking Jan Beulich
2026-09-30 11:42 ` [PATCH v2 1/5] x86/pass-through: alter locking around pt_irq_{create,destroy}_bind() Jan Beulich
2026-10-28 14:33   ` Roger Pau Monné
2026-10-28 15:21     ` Jan Beulich
2026-10-28 15:36       ` Roger Pau Monné
2026-09-30 11:42 ` [PATCH v2 2/5] x86/vPCI: tighten locking assertions Jan Beulich
2026-09-30 11:43 ` [PATCH v2 3/5] x86/pass-through: use simpler locking primitives in pt_irq_{create,destroy}_bind() Jan Beulich
2026-09-30 11:43 ` [PATCH v2 4/5] x86/vPCI: make better use of "pdev" in vpci_msix_arch_print() Jan Beulich
2026-10-28 14:38   ` Roger Pau Monné [this message]
2026-09-30 11:43 ` [PATCH v2 5/5] x86/vMSI: avoid "goto" in msixtbl_pt_unregister() Jan Beulich
2026-10-28 14:51   ` Roger Pau Monné

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=auII7rNEJN-xvkql@Mac.lan \
    --to=roger@xenproject.org \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=teddy.astie@vates.tech \
    --cc=xen-devel@lists.xenproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.