From: Jeremy Dean Clifton <gservice341@gmail.com>
To: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>,
Alex Elder <elder@ieee.org>
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 v2] staging: greybus: replace PTR_ERR() with %pe in error messages
Date: Wed, 14 Oct 2026 10:43:46 -0600 [thread overview]
Message-ID: <6d881c38-33f7-48e0-88d0-4d16170c24e6@gmail.com> (raw)
In-Reply-To: <as6mC7sZnpqIKxN6@user>
On 10/13/26 3:43 PM, Yalagada Pavan Kumar wrote:
> On Tue, Oct 13, 2026 at 03:11:51PM -0500, Alex Elder wrote:
>> On 10/12/26 9:24 PM, 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>
>>
>>
>> Generally I think what you're doing is OK. It looks
>> like %pe is better than just %d, because it prints
>> the error *name* for the pointer-coded error.
>>
>> But I have two general questions about this effort:
>>
>> - There are other places in the Greybus code (even in
>> just the staging source files) where this exact same
>> thing could be done. Why limit this to "fw-core.c" only?
>
> I initially limited the change to "fw-core.c" because I was
> focusing on the error messages in that file.
>
>>
>> - Do you think that all Greybus error messages should be
>> converted to use %pe (passing ERR_PTR() if necessary)
>> instead of %d for showing the error number?
>
> Using %pe prints the error name instead of just the
> error number, which makes the error messages easier
> to understand.
>
> For example, the current message is:
>
> failed to create download connection (-12)
>
> with %pe, it becomes:
>
> failed to create download connection (-ENOMEM)
>
> I think the second message is easier to understand because
> it shows the error name instead of just error number.
>
> I also found other PTR_ERR() calls in Greybus. some of them
> are used to return error codes and should remain unchanged.
>
> For example, in fw-core.c:
>
> if (IS_ERR(connection)) {
> ret = PTR_ERR(connection);
> dev_err(&bundle->dev,
> "failed to create management connection (%pe)\n",
> connection);
> goto err_destroy_connections;
> }
>
> Here, PTR_ERR(connection) is needed to store the error code in ret
> for the error-handling path, while passing connection to %pe makes
> the error message more readable.
>
>>
>> I think your suggested change is a net positive, but
>> doing it in some spots but not others means it is
>> adding a bit of inconsistency.
>
> I agree that similar cases elsewhere in Greybus are worth
> checking to keep error reporting consistent. I will look
> at the other Greybus files for cases where using %pe would
> be appropriate.
>
> Would you prefer me to extend this change to the other
> relevant Greybus files, or keep this patch focused on
> fw-core.c and submit a separate patch for the remaining
> changes?
Also, you could coordinate something with Julia to use Coccinelle for
this. Using regular expressions, you could programmatically find all the
places where %pe and connection can be in place of %d or %ld and the
return from PTR_ERR().
Jeremy Clifton
next prev parent reply other threads:[~2026-10-14 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 2:24 pavankumaryalagada
2026-10-13 20:11 ` Alex Elder
2026-10-13 21:43 ` Yalagada Pavan Kumar
2026-10-14 13:32 ` Alex Elder
2026-10-14 16:40 ` Yalagada Pavan Kumar
2026-10-14 19:14 ` Julia Lawall
2026-10-15 1:23 ` Alex Elder
2026-10-14 16:43 ` Jeremy Dean Clifton [this message]
2026-10-14 19:15 ` Julia Lawall
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=6d881c38-33f7-48e0-88d0-4d16170c24e6@gmail.com \
--to=gservice341@gmail.com \
--cc=elder@ieee.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=pavankumaryalagada@gmail.com \
--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®