All of lore.kernel.org
 help / color / mirror / Atom feed
From: dmkhn@proton.me
To: Jason Andryuk <jason.andryuk@amd.com>
Cc: xen-devel@lists.xenproject.org, "Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH] xen/vpci: Fix msix existing mapping printk
Date: Wed, 23 Apr 2025 21:36:35 +0000	[thread overview]
Message-ID: <aAldXz0zFDc9md0p@kraken> (raw)
In-Reply-To: <20250423212229.32721-1-jason.andryuk@amd.com>

On Wed, Apr 23, 2025 at 05:22:29PM -0400, Jason Andryuk wrote:
> The format string lacks a space, so mfn and type run together:
> (XEN) d0v0 0000:06:00.7: existing mapping (mfn: 753037type: 0) at 0x1 clobbers MSIX MMIO area
> 
> Add a space.
> 
> Signed-off-by: Jason Andryuk <jason.andryuk@amd.com>

Reviewed-by: Denis Mukhin <dmukhin@ford.com>

> ---
>  xen/drivers/vpci/msix.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/xen/drivers/vpci/msix.c b/xen/drivers/vpci/msix.c
> index f3804ce047..499810b238 100644
> --- a/xen/drivers/vpci/msix.c
> +++ b/xen/drivers/vpci/msix.c
> @@ -666,7 +666,7 @@ int vpci_make_msix_hole(const struct pci_dev *pdev)
>                  put_gfn(d, start);
>                  gprintk(XENLOG_WARNING,
>                          "%pp: existing mapping (mfn: %" PRI_mfn
> -                        "type: %d) at %#lx clobbers MSIX MMIO area\n",
> +                        " type: %d) at %#lx clobbers MSIX MMIO area\n",
>                          &pdev->sbdf, mfn_x(mfn), t, start);
>                  return -EEXIST;
>              }
> --
> 2.49.0
> 
> 



  parent reply	other threads:[~2025-04-23 21:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-23 21:22 [PATCH] xen/vpci: Fix msix existing mapping printk Jason Andryuk
2025-04-23 21:32 ` Jason Andryuk
2025-04-23 21:36 ` dmkhn [this message]
2025-04-24  6:18 ` Jan Beulich
2025-04-24 14:03   ` Jason Andryuk

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=aAldXz0zFDc9md0p@kraken \
    --to=dmkhn@proton.me \
    --cc=jason.andryuk@amd.com \
    --cc=roger.pau@citrix.com \
    --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.