From: Greg KH <gregkh@linuxfoundation.org>
To: S Tarun Kumar Lywait <tarun.k.lywait@gmail.com>
Cc: johan@kernel.org, elder@kernel.org, greybus-dev@lists.linaro.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: greybus: camera: Fix function declaration alignment
Date: Wed, 9 Sep 2026 09:42:50 +0200 [thread overview]
Message-ID: <2026090928-playtime-carwash-eb07@gregkh> (raw)
In-Reply-To: <20260908171011.4122-1-tarun.k.lywait@gmail.com>
On Tue, Sep 08, 2026 at 10:40:11PM +0530, S Tarun Kumar Lywait wrote:
> Adhere to Linux kernel coding style. Reported by checkpatch:
> CHECK: Alignment should match open parenthesis
>
> Signed-off-by: S Tarun Kumar Lywait <tarun.k.lywait@gmail.com>
> ---
> drivers/staging/greybus/camera.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/greybus/camera.c b/drivers/staging/greybus/camera.c
> index 62b55bb28408..9853bd60ff27 100644
> --- a/drivers/staging/greybus/camera.c
> +++ b/drivers/staging/greybus/camera.c
> @@ -263,9 +263,10 @@ static int gb_camera_get_max_pkt_size(struct gb_camera *gcam,
> * Validate the stream configuration response verifying padding is correctly
> * set and the returned number of streams is supported
> */
> -static const int gb_camera_configure_streams_validate_response(struct gb_camera *gcam,
> - struct gb_camera_configure_streams_response *resp,
> - unsigned int nstreams)
> +static const int gb_camera_configure_streams_validate_response
> + (struct gb_camera *gcam,
That does not look correct at all, what tool asked you to make this type
of change?
thanks,
greg k-h
next prev parent reply other threads:[~2026-09-09 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 17:10 S Tarun Kumar Lywait
2026-09-09 7:42 ` Greg KH [this message]
2026-09-10 15:03 ` S Tarun Kumar Lywait
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=2026090928-playtime-carwash-eb07@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=elder@kernel.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=tarun.k.lywait@gmail.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
all inboxes | Powered by JetHome®