From: Brett Creeley <bcreeley@amd.com>
To: Alok Tiwari <alok.a.tiwari@oracle.com>,
shannon.nelson@amd.com, brett.creeley@amd.com,
eperezma@redhat.com, mst@redhat.com, jasowang@redhat.com,
xuanzhuo@linux.alibaba.com, virtualization@lists.linux.dev
Cc: alok.a.tiwarilinux@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vdpa/pds: use %pe for ERR_PTR() in event handler registration
Date: Thu, 23 Oct 2025 15:24:51 -0700 [thread overview]
Message-ID: <53d8d0e0-d7d7-481d-8f86-2a71c6503362@amd.com> (raw)
In-Reply-To: <20251018174705.1511982-1-alok.a.tiwari@oracle.com>
On 10/18/2025 10:46 AM, Alok Tiwari wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
> Use %pe instead of %ps when printing ERR_PTR() values. %ps is intended
> for string pointers, while %pe correctly prints symbolic error names
> for error pointers returned via ERR_PTR().
> This shows the returned error value more clearly.
>
> Fixes: 67f27b8b3a34 ("pds_vdpa: subscribe to the pds_core events")
> Signed-off-by: Alok Tiwari <alok.a.tiwari@oracle.com>
> ---
> drivers/vdpa/pds/vdpa_dev.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
LGTM. Thanks.
Reviewed-by: Brett Creeley <brett.creeley@amd.com>
>
> diff --git a/drivers/vdpa/pds/vdpa_dev.c b/drivers/vdpa/pds/vdpa_dev.c
> index 36f61cc96e21..43426bd971ac 100644
> --- a/drivers/vdpa/pds/vdpa_dev.c
> +++ b/drivers/vdpa/pds/vdpa_dev.c
> @@ -51,7 +51,7 @@ static int pds_vdpa_register_event_handler(struct pds_vdpa_device *pdsv)
> err = pdsc_register_notify(nb);
> if (err) {
> nb->notifier_call = NULL;
> - dev_err(dev, "failed to register pds event handler: %ps\n",
> + dev_err(dev, "failed to register pds event handler: %pe\n" > ERR_PTR(err));
> return -EINVAL;
> }
> --
> 2.50.1
>
prev parent reply other threads:[~2025-10-23 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-18 17:46 Alok Tiwari
2025-10-23 22:24 ` Brett Creeley [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=53d8d0e0-d7d7-481d-8f86-2a71c6503362@amd.com \
--to=bcreeley@amd.com \
--cc=alok.a.tiwari@oracle.com \
--cc=alok.a.tiwarilinux@gmail.com \
--cc=brett.creeley@amd.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=shannon.nelson@amd.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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
all inboxes | Powered by JetHome®