From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: "Darshan R." <rathod.darshan.0896@gmail.com>
Cc: hansg@kernel.org, mchehab@kernel.org, gregkh@linuxfoundation.org,
sakari.ailus@linux.intel.com, andy@kernel.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev, jogidishank503@gmail.com
Subject: Re: [PATCH] staging: media: atomisp: Fix indentation and styling in output kernel code
Date: Mon, 28 Jul 2025 22:08:50 +0200 [thread overview]
Message-ID: <CAHp75Vfq6P2osMc5A5TZ5Usgyc7mFGNme6TmCQugTE1=8c1zAg@mail.gmail.com> (raw)
In-Reply-To: <20250728072822.10730-1-rathod.darshan.0896@gmail.com>
On Mon, Jul 28, 2025 at 9:27 AM Darshan R.
<rathod.darshan.0896@gmail.com> wrote:
>
> Updated the formatting of function definitions and if statements to match
> kernel coding standards. This helps with readability and consistency across
> the codebase.
>
> These are non-functional changes aimed at preparing the driver for eventual
> mainline readiness by addressing common checkpatch warnings.
...
> void
> ia_css_output_encode(
And what is about the above?
> - struct sh_css_isp_output_params *to,
> - const struct ia_css_output_config *from,
> - unsigned int size)
> + struct sh_css_isp_output_params *to,
> + const struct ia_css_output_config *from,
> + unsigned int size)
...
> int ia_css_output1_config(struct sh_css_isp_output_isp_config *to,
Seems too much space between _config and *to.
> - const struct ia_css_output1_configuration *from,
> + const struct ia_css_output1_configuration *from,
> unsigned int size)
...
> int ia_css_output0_configure(const struct ia_css_binary *binary,
Ditto.
> - const struct ia_css_frame_info *info)
> + const struct ia_css_frame_info *info)
...
The rest of the code is also subject to the above comments.
...
Btw, somebody else already submitted the similar changes.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-07-28 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 7:28 [PATCH] staging: media: atomisp: Fix indentation and styling in output kernel code Darshan R.
2025-07-28 20:08 ` Andy Shevchenko [this message]
2025-07-29 5:15 ` Darshan Rathod
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='CAHp75Vfq6P2osMc5A5TZ5Usgyc7mFGNme6TmCQugTE1=8c1zAg@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=jogidishank503@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=rathod.darshan.0896@gmail.com \
--cc=sakari.ailus@linux.intel.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;
as well as URLs for NNTP newsgroup(s).