From: Greg KH <gregkh@linuxfoundation.org>
To: Zhan Xusheng <zhanxusheng1024@gmail.com>
Cc: linux-staging@lists.linux.dev, Zhan Xusheng <zhanxusheng@xiaomi.com>
Subject: Re: [PATCH 1/4] staging: greybus: spilib: fix function parameter indentation
Date: Mon, 22 Dec 2025 09:45:02 +0100 [thread overview]
Message-ID: <2025122207-friday-santa-3251@gregkh> (raw)
In-Reply-To: <20251219063415.46818-2-zhanxusheng@xiaomi.com>
On Fri, Dec 19, 2025 at 02:34:12PM +0800, Zhan Xusheng wrote:
> Fix checkpatch.pl warning:
> "Alignment should match open parenthesis"
> by aligning wrapped function parameters with
> the opening parenthesis.
>
> Signed-off-by: Zhan Xusheng <zhanxusheng@xiaomi.com>
> ---
> drivers/staging/greybus/spilib.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/greybus/spilib.c b/drivers/staging/greybus/spilib.c
> index 24e9c909fa02..416ca27a25ce 100644
> --- a/drivers/staging/greybus/spilib.c
> +++ b/drivers/staging/greybus/spilib.c
> @@ -159,8 +159,10 @@ 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)
> +static struct gb_operation *
> +gb_spi_operation_create(struct gb_spilib *spi,
> + struct gb_connection *connection,
> + struct spi_message *msg)
This is where things get messy :(
The original is still best, as you can see the function name, and the
return type, on the same line, which many search tools really want to
show you when searching code.
So the existing code is fine, no need to worry about this warning here.
thanks,
greg k-h
next prev parent reply other threads:[~2025-12-22 8:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 6:34 [PATCH 0/4] greybus: staging fixes and cleanups Zhan Xusheng
2025-12-19 6:34 ` [PATCH 1/4] staging: greybus: spilib: fix function parameter indentation Zhan Xusheng
2025-12-22 8:45 ` Greg KH [this message]
2025-12-19 6:34 ` [PATCH 2/4] staging: greybus: audio: avoid macro with side effects Zhan Xusheng
2025-12-22 8:46 ` Greg KH
2025-12-19 6:34 ` [PATCH 3/4] staging: greybus: gb-camera: use BIT() macro and fix formatting Zhan Xusheng
2025-12-22 8:46 ` Greg KH
2025-12-19 6:34 ` [PATCH 4/4] staging: greybus: greybus_firmware: fix long macro lines Zhan Xusheng
2025-12-22 8:47 ` Greg KH
2025-12-22 15:40 ` [PATCH 1/4] staging: greybus: gb-camera: use BIT() macro and fix formatting Zhan Xusheng
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=2025122207-friday-santa-3251@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-staging@lists.linux.dev \
--cc=zhanxusheng1024@gmail.com \
--cc=zhanxusheng@xiaomi.com \
/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