mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>
To: Jeremy Clifton <gservice341@gmail.com>
Cc: johan@kernel.org, gregkh@linuxfoundation.org, vireshk@kernel.org,
	elder@kernel.org, greybus-dev@lists.linaro.org,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	outreachy@lists.linux.dev
Subject: Re: [PATCH] staging: greybus: replace PTR_ERR() with %pe in error messages
Date: Tue, 13 Oct 2026 00:01:33 +0530	[thread overview]
Message-ID: <as0nhVbagZa8Birm@user> (raw)
In-Reply-To: <CAC2RYzLMQSOi961mmyNkK1aVuMDafXdvRj_mCEAZQnU37sKA8w@mail.gmail.com>

On Mon, Oct 12, 2026 at 11:57:26AM -0600, Jeremy Clifton wrote:
> For this patch I have only one immediate suggestion.
> 
> The firmware management case (case GREYBUS_PROTOCOL_FW_MANAGEMENT:)
> should match the other cases. Found around line 96.

Thanks for the review. I'll update the firmware management case to use %pe
for consistency and send a revised patch.

Thanks,
Pavan

> 
> You've changed the pointer variable to display and this seems correct.
> 
> For consistency, each should match.
> 
> On Mon, Oct 12, 2026 at 11:00 AM <pavankumaryalagada@gmail.com> wrote:
> >
> > From: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>
> >
> > Use %pe to print error pointers directly and display their
> > error names.
> >
> > Keep the other PTR_ERR() call because its return value is
> > needed for ret.
> >
> > Signed-off-by: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>
> > ---
> >  drivers/staging/greybus/fw-core.c | 12 ++++++------
> >  1 file changed, 6 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/staging/greybus/fw-core.c b/drivers/staging/greybus/fw-core.c
> > index 2016a74f137f..7053afa9ab3e 100644
> > --- a/drivers/staging/greybus/fw-core.c
> > +++ b/drivers/staging/greybus/fw-core.c
> > @@ -112,8 +112,8 @@ static int gb_fw_core_probe(struct gb_bundle *bundle,
> >                         connection = gb_connection_create(bundle, cport_id,
> >                                                           gb_fw_download_request_handler);
> >                         if (IS_ERR(connection)) {
> > -                               dev_err(&bundle->dev, "failed to create download connection (%ld)\n",
> > -                                       PTR_ERR(connection));
> > +                               dev_err(&bundle->dev, "failed to create download connection (%pe)\n",
> > +                                       connection);
> >                         } else {
> >                                 fw_core->download_connection = connection;
> >                         }
> > @@ -131,8 +131,8 @@ static int gb_fw_core_probe(struct gb_bundle *bundle,
> >                         connection = gb_connection_create(bundle, cport_id,
> >                                                           NULL);
> >                         if (IS_ERR(connection)) {
> > -                               dev_err(&bundle->dev, "failed to create SPI connection (%ld)\n",
> > -                                       PTR_ERR(connection));
> > +                               dev_err(&bundle->dev, "failed to create SPI connection (%pe)\n",
> > +                                       connection);
> >                         } else {
> >                                 fw_core->spi_connection = connection;
> >                         }
> > @@ -149,8 +149,8 @@ static int gb_fw_core_probe(struct gb_bundle *bundle,
> >                         connection = gb_connection_create(bundle, cport_id,
> >                                                           NULL);
> >                         if (IS_ERR(connection)) {
> > -                               dev_err(&bundle->dev, "failed to create Authentication connection (%ld)\n",
> > -                                       PTR_ERR(connection));
> > +                               dev_err(&bundle->dev, "failed to create Authentication connection (%pe)\n",
> > +                                       connection);
> >                         } else {
> >                                 fw_core->cap_connection = connection;
> >                         }
> > --
> > 2.43.0
> >
> >

      reply	other threads:[~2026-10-12 18:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12 17:00 pavankumaryalagada
2026-10-12 17:57 ` Jeremy Clifton
2026-10-12 18:31   ` Yalagada Pavan Kumar [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=as0nhVbagZa8Birm@user \
    --to=pavankumaryalagada@gmail.com \
    --cc=elder@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=gservice341@gmail.com \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=outreachy@lists.linux.dev \
    --cc=vireshk@kernel.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 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®