From: Alex Elder <elder@ieee.org>
To: Yalagada Pavan Kumar <pavankumaryalagada@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, gservice341@gmail.com
Subject: Re: [PATCH v2] staging: greybus: replace PTR_ERR() with %pe in error messages
Date: Wed, 14 Oct 2026 08:32:54 -0500 [thread overview]
Message-ID: <26a2a4af-5d27-4bd5-b284-3758fa7a67b2@ieee.org> (raw)
In-Reply-To: <as6mC7sZnpqIKxN6@user>
On 10/13/26 4:43 PM, Yalagada Pavan Kumar wrote:
>> 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?
I guess I mainly wanted to understand your intent. I don't
really mind your proposed change, but I would really prefer
to have it be part of an overall plan to upgrade all error
messages this way.
Ideally error (and other) messages are done consistently,
and so changing them in just one file sort of raises a flag
for me.
Can you survey the messages elsewhere in the Greybus code
and get a sense of how much work it will be to do this
comprehensively? Your current patch affects four spots in
one source file; how many others would there be?
And if updating everything is a task you're willing to do,
then I think I would prefer you extend this change.
-Alex
next prev parent reply other threads:[~2026-10-14 13:32 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 [this message]
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
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=26a2a4af-5d27-4bd5-b284-3758fa7a67b2@ieee.org \
--to=elder@ieee.org \
--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=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®