From: Alex Elder <elder@riscstar.com>
To: Erick Karanja <karanja99erick@gmail.com>,
outreachy@lists.linux.dev, johan@kernel.org, elder@kernel.org,
gregkh@linuxfoundation.org
Cc: greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: greybus: Alignment warning
Date: Tue, 25 Mar 2025 07:15:01 -0500 [thread overview]
Message-ID: <a5477192-ee6f-4273-b7b4-1d9dbd7e7b50@riscstar.com> (raw)
In-Reply-To: <20250322065800.21361-1-karanja99erick@gmail.com>
On 3/22/25 1:58 AM, Erick Karanja wrote:
> Correct the alignment of the parameters to match the open parenthesis.
>
> Reported by checkpatch:
>
> CHECK: Alignment should match open parenthesis
I think this change is OK. However you'll notice that checkpatch.pl
has three categories of issues that get reported: errors, warnings,
and checks. These are in decreasing order of severity.
Alignment issues like this are just "checks", which means they are
minor nits that are often not considered a "real" problem. In many
cases, white space variances like this are done intentionally, to
make the code more readable, or sometimes simply because the code
that surrounds it used a different convention for alignment (some
people simply align to an even number of tabs, for example).
In this case, the change doesn't make the "look" of the code any
worse, and doesn't reduce readability. It furthermore gets rid
of spaces after a tab that do *not* lead to the suggested alignment.
It probably isn't a necessary change, but I think it's reasonable.
I write all this to explain that these sorts of changes are in many
cases rejected.
I'll leave it to Greg to accept this, or offer a second opinion.
Reviewed-by: Alex Elder <elder@riscstar.com>
>
> Signed-off-by: Erick Karanja <karanja99erick@gmail.com>
> ---
> drivers/staging/greybus/camera.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/greybus/camera.c b/drivers/staging/greybus/camera.c
> index 5d80ace41d8e..ec9fddfc0b14 100644
> --- a/drivers/staging/greybus/camera.c
> +++ b/drivers/staging/greybus/camera.c
> @@ -1165,8 +1165,8 @@ static int gb_camera_debugfs_init(struct gb_camera *gcam)
> gcam->debugfs.buffers[i].length = 0;
>
> debugfs_create_file_aux(entry->name, entry->mask,
> - gcam->debugfs.root, gcam, entry,
> - &gb_camera_debugfs_ops);
> + gcam->debugfs.root, gcam, entry,
> + &gb_camera_debugfs_ops);
> }
>
> return 0;
prev parent reply other threads:[~2025-03-25 12:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 6:58 [PATCH] staging: greybus: Alignment warning Erick Karanja
2025-03-25 12:15 ` 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=a5477192-ee6f-4273-b7b4-1d9dbd7e7b50@riscstar.com \
--to=elder@riscstar.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=karanja99erick@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
/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