[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VcFSbLwqot0Rrm=141Y-mCQUuFqNGn=DnfKSSYp-31vcg@mail.gmail.com>
Date: Sun, 22 Jun 2025 23:42:03 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: LiangCheng Wang <zaq14760@...il.com>
Cc: Andy Shevchenko <andy@...nel.org>, Hans de Goede <hansg@...nel.org>,
Mauro Carvalho Chehab <mchehab@...nel.org>, Sakari Ailus <sakari.ailus@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>, linux-media@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-staging@...ts.linux.dev
Subject: Re: [PATCH v3] staging: media: atomisp: fix coding style in ia_css_output.host.c
On Sun, Jun 22, 2025 at 6:42 AM LiangCheng Wang <zaq14760@...il.com> wrote:
>
> Fix multiple checkpatch.pl ERRORs and coding style issues:
>
> - Use tabs instead of spaces for indentation
> - Move trailing `if` statements to multiline format
> - Remove excessive space between type and asterisk in function
> arguments
>
> This cleanup improves code readability and follows Linux kernel
> coding standards.
Change looks okay now. The question is are there only these
problematic places or more? Can you double check the entire driver for
these?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists