mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Elder <elder@ieee.org>
To: Okhuomon Ajayi <okhuomonajayi54@gmail.com>, outreachy@lists.linux.dev
Cc: Viresh Kumar <vireshk@kernel.org>,
	Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: greybus: fw-management: fix argument alignment
Date: Mon, 19 Oct 2026 07:18:37 -0500	[thread overview]
Message-ID: <2977f214-00e1-43e5-b286-eecadffcab00@ieee.org> (raw)
In-Reply-To: <20261018224241.46011-1-okhuomonajayi54@gmail.com>

On 10/18/26 5:42 PM, Okhuomon Ajayi wrote:
> Align the arguments of the fw_mgmt_load_and_validate_operation()
> call with the opening parenthesis and split them across separate
> lines to avoid an overly long line.
> 
> CHECK: Alignment should match open parenthesis

So this was found with "make C=1".  And the checker tool used
was sparse?  If so, that bit of context for this message would
be helpful to add.

Also, I tend to ask this a log on these small one-off patches:
Are there any other instances you see of this particular
warning?  I *know* not all of them can be fixed as neatly
as this one, but are there cases where aligning arguments
this way still preserves readability?  (Greybus code also
generally fits within 80 columns.)

If there are, I think it would be good to fix them together
(in one patch, or possibly in a series, one per file).

Other than those comments, this change looks good to me.

Reviewed-by: Alex Elder <elder@riscstar.com>

> Signed-off-by: Okhuomon Ajayi <okhuomonajayi54@gmail.com>
> ---
>   drivers/staging/greybus/fw-management.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/greybus/fw-management.c b/drivers/staging/greybus/fw-management.c
> index 5d01da6b6eb9..e20e9136c106 100644
> --- a/drivers/staging/greybus/fw-management.c
> +++ b/drivers/staging/greybus/fw-management.c
> @@ -434,7 +434,8 @@ static int fw_mgmt_ioctl(struct fw_mgmt *fw_mgmt, unsigned int cmd,
>   			return -EFAULT;
>   
>   		ret = fw_mgmt_load_and_validate_operation(fw_mgmt,
> -				intf_load.load_method, intf_load.firmware_tag);
> +							  intf_load.load_method,
> +							  intf_load.firmware_tag);
>   		if (ret)
>   			return ret;
>   


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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18 22:42 Okhuomon Ajayi
2026-10-19  1:47 ` Ethan Tidmore
2026-10-19 12:18 ` Alex Elder [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=2977f214-00e1-43e5-b286-eecadffcab00@ieee.org \
    --to=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=okhuomonajayi54@gmail.com \
    --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®