From: Nandha Kumar Singaram <nandhakumar.singaram@gmail.com>
To: Alex Elder <elder@ieee.org>
Cc: Viresh Kumar <vireshk@kernel.org>,
Johan Hovold <johan@kernel.org>,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, kumaran.4353@gmail.com
Subject: Re: [PATCH v2 1/3] staging: greybus: camera: Alignment should match open parenthesis
Date: Sat, 28 Oct 2023 13:22:20 -0700 [thread overview]
Message-ID: <20231028202220.GA2432@ubuntu> (raw)
In-Reply-To: <7703f20b-60e1-4140-8380-5a5157bc49b0@ieee.org>
On Thu, Oct 26, 2023 at 01:18:04PM -0500, Alex Elder wrote:
> On 10/22/23 7:15 AM, Nandha Kumar Singaram wrote:
> > Adhere to linux coding style. Reported by checkpatch.pl:
> > CHECK: Alignment should match open parenthesis
>
> Generally, the result of this patch in isolation looks OK.
> But when you compare it with your next patch, what you're
> doing here becomes inconsistent with the indentation used
> for the function arguments there.
>
> There is value in consistency as advocated by checkpatch,
> but there's also value in consistency within a single
> source file.
>
> I'd stay away from these white space changes.
>
> -Alex
>
> > Signed-off-by: Nandha Kumar Singaram <nandhakumar.singaram@gmail.com>
> > ---
> > drivers/staging/greybus/camera.c | 10 +++++-----
> > 1 file changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/staging/greybus/camera.c b/drivers/staging/greybus/camera.c
> > index ae49e37a87e9..6516e7efaab9 100644
> > --- a/drivers/staging/greybus/camera.c
> > +++ b/drivers/staging/greybus/camera.c
> > @@ -220,7 +220,7 @@ static int gb_camera_operation_sync_flags(struct gb_connection *connection,
> > }
> > static int gb_camera_get_max_pkt_size(struct gb_camera *gcam,
> > - struct gb_camera_configure_streams_response *resp)
> > + struct gb_camera_configure_streams_response *resp)
> > {
> > unsigned int max_pkt_size = 0;
> > unsigned int i;
> > @@ -378,8 +378,8 @@ struct ap_csi_config_request {
> > #define GB_CAMERA_CSI_CLK_FREQ_MARGIN 150000000U
> > static int gb_camera_setup_data_connection(struct gb_camera *gcam,
> > - struct gb_camera_configure_streams_response *resp,
> > - struct gb_camera_csi_params *csi_params)
> > + struct gb_camera_configure_streams_response *resp,
> > + struct gb_camera_csi_params *csi_params)
> > {
> > struct ap_csi_config_request csi_cfg;
> > struct gb_connection *conn;
> > @@ -783,8 +783,8 @@ static ssize_t gb_camera_op_capabilities(void *priv, char *data, size_t len)
> > }
> > static int gb_camera_op_configure_streams(void *priv, unsigned int *nstreams,
> > - unsigned int *flags, struct gb_camera_stream *streams,
> > - struct gb_camera_csi_params *csi_params)
> > + unsigned int *flags, struct gb_camera_stream *streams,
> > + struct gb_camera_csi_params *csi_params)
> > {
> > struct gb_camera *gcam = priv;
> > struct gb_camera_stream_config *gb_streams;
>
Thanks Alex for the review.
yeah, I understood about the indentation issue when comparing
to other patch but fixing the indentation there results in
another checkpatch check(CHECK: line length of 113 exceeds 100
columns) so didn't added any change over there.
Regards,
Nandha Kumar
next prev parent reply other threads:[~2023-10-28 20:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 12:13 [PATCH v2 0/3] staging: greybus: Coding style cleanup patches Nandha Kumar Singaram
2023-10-22 12:15 ` [PATCH v2 1/3] staging: greybus: camera: Alignment should match open parenthesis Nandha Kumar Singaram
2023-10-26 18:18 ` Alex Elder
2023-10-28 20:22 ` Nandha Kumar Singaram [this message]
2023-10-22 12:18 ` [PATCH v2 2/3] staging: greybus: camera: Modify lines end with a '(' Nandha Kumar Singaram
2023-10-22 12:22 ` [PATCH v2 3/3] staging: greybus: bootrom: fixed prefer using ftrace warning Nandha Kumar Singaram
2023-10-26 18:20 ` Alex Elder
2023-10-28 20:25 ` Nandha Kumar Singaram
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=20231028202220.GA2432@ubuntu \
--to=nandhakumar.singaram@gmail.com \
--cc=elder@ieee.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=kumaran.4353@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.