From: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>
To: Alex Elder <elder@ieee.org>
Cc: gregkh@linuxfoundation.org, outreachy@lists.linux.dev,
pure.logic@nexus-software.ie, johan@kernel.org, elder@kernel.org,
rmfrfs@gmail.com, vireshk@kernel.org,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, ethantidmore06@gmail.com
Subject: Re: [PATCH v2] staging: greybus: Align function arguments
Date: Wed, 21 Oct 2026 09:49:51 +0530 [thread overview]
Message-ID: <atg9Zwie6-Dva-Xb@user> (raw)
In-Reply-To: <7e71d57b-f3c7-48b7-bcdf-75254ee87cdd@ieee.org>
On Tue, Oct 20, 2026 at 09:00:03AM -0500, Alex Elder wrote:
> On 10/17/26 3:44 AM, pavankumaryalagada@gmail.com wrote:
> > From: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>
> >
> > Align the function arguments to follow the coding style and
> > improve readability, addressing the alignment warning reported by
> > checkpatch.pl
> >
> > Signed-off-by: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>
>
> This patch is OK, and it's a good kind of thing to do for
> getting your feet wet with sending out patches for review.
Thank you for reviewing my patch.
>
> But I encourage you to try to really *read* and understand
> the code, and see if you can find anything you think is wrong,
> or some bit of code or comments that you think could be more
> clear.
>
I will try to understand the code better and look for ways to
improve it.
> I just scanned through "loopback.c" and one minor change (to
> *code*) you could try is using fsleep() in one place that
> uses other functions to delay.
I will look into this and work on it.
>
> Another thing you could look for is printf-style format
> specifiers. I see more than one place where an unsigned
> value uses %d (which, for large values, produce misleading
> results).
I will also check the format specifiers and make sure they
match the variable types.
>
> These suggestions aren't especially complex, but my hope
> is they lead you further into understanding the code and
> not relying heavily on checkpatch.pl to find things.
I will keep these suggestions in mind when working on future
patches.
Thanks,
Pavan
>
> Anyway, this change looks fine to me.
>
> Reviewed-by: Alex Elder <elder@riscstar.com>
> > ---
> > v2:
> > - Rebased onto staging-next.
> > v1: https://lore.kernel.org/outreachy/C560A15E-6F28-4FC8-8BE2-277B503340AD@inria.fr/T/#t
> >
> > drivers/staging/greybus/loopback.c | 3 ++-
> > drivers/staging/greybus/spilib.c | 3 ++-
> > 2 files changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/staging/greybus/loopback.c b/drivers/staging/greybus/loopback.c
> > index fe48a687377a..efc69c10cffe 100644
> > --- a/drivers/staging/greybus/loopback.c
> > +++ b/drivers/staging/greybus/loopback.c
> > @@ -652,7 +652,8 @@ static int gb_loopback_request_handler(struct gb_operation *operation)
> > }
> > if (!gb_operation_response_alloc(operation,
> > - len + sizeof(*response), GFP_KERNEL)) {
> > + len + sizeof(*response),
> > + GFP_KERNEL)) {
> > dev_err(dev, "error allocating response\n");
> > return -ENOMEM;
> > }
> > diff --git a/drivers/staging/greybus/spilib.c b/drivers/staging/greybus/spilib.c
> > index e4d1ae8308aa..c1982f3fb931 100644
> > --- a/drivers/staging/greybus/spilib.c
> > +++ b/drivers/staging/greybus/spilib.c
> > @@ -160,7 +160,8 @@ static struct spi_transfer *get_next_xfer(struct spi_transfer *xfer,
> > /* Routines to transfer data */
> > static struct gb_operation *gb_spi_operation_create(struct gb_spilib *spi,
> > - struct gb_connection *connection, struct spi_message *msg)
> > + struct gb_connection *connection,
> > + struct spi_message *msg)
> > {
> > struct gb_spi_transfer_request *request;
> > struct spi_device *dev = msg->spi;
>
prev parent reply other threads:[~2026-10-21 4:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 8:44 pavankumaryalagada
2026-10-20 14:00 ` Alex Elder
2026-10-21 4:19 ` 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=atg9Zwie6-Dva-Xb@user \
--to=pavankumaryalagada@gmail.com \
--cc=elder@ieee.org \
--cc=elder@kernel.org \
--cc=ethantidmore06@gmail.com \
--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=pure.logic@nexus-software.ie \
--cc=rmfrfs@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®