From: Thomas Andreatta <thomasandreatta2000@gmail.com>
To: andy@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
thomas.andreatta2000@gmail.com
Subject: Re: [PATCH 2/2] Staging: media: atomisp: style corrections
Date: Sun, 27 Apr 2025 16:24:22 +0200 [thread overview]
Message-ID: <20250427142422.88271-1-thomas.andreatta2000@gmail.com> (raw)
In-Reply-To: <CAHp75Vef0DuupHr9CAaU9qnDEw6O6KRPaO51uzrKXPwvfAiiJA@mail.gmail.com>
On Sun, Apr 27, 2025 at 12:41:34PM +0300, Andy Shevchenko wrote:
> On Sat, Apr 26, 2025 at 11:15 PM Thomas Andreatta
> <thomasandreatta2000@gmail.com> wrote:
> >
> > Corrected consistent spacing around '*' and braces positions
>
> Missed period.
> And what is the correct spacing and why?
I agree that the spacing looks weird and I questioned it too, but the script
checkpatch.pl highlights as error:
`sh_css.c:336: ERROR: need consistent spacing around '*' (ctx:WxV)`
`sh_css.c:338: ERROR: need consistent spacing around '*' (ctx:WxV)`
Should this be ignored because the script tries its best and it becomes common
sense that the suggested spacing is "wrong"?
>
> ...
>
> > static unsigned int get_crop_lines_for_bayer_order(const struct
> > - ia_css_stream_config *config);
> > + ia_css_stream_config * config);
> > static unsigned int get_crop_columns_for_bayer_order(const struct
> > - ia_css_stream_config *config);
> > + ia_css_stream_config * config);
>
> No, this makes it the opposite. Please, read Coding Style if it sheds
> a light on this. In any case the kernel style is to avoid spacing
> between asterisk and name.
Understood. I'll resubmit with the correct spacing.
Thanks,
Thomas
next prev parent reply other threads:[~2025-04-27 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-26 20:15 Thomas Andreatta
2025-04-27 9:41 ` Andy Shevchenko
2025-04-27 14:24 ` Thomas Andreatta [this message]
2025-04-27 18:49 ` Andy Shevchenko
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=20250427142422.88271-1-thomas.andreatta2000@gmail.com \
--to=thomasandreatta2000@gmail.com \
--cc=andy@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=thomas.andreatta2000@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®