[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72nu3KKovTfkoSofNX05ScvP83Dc2GusP7JJwWD1g2rbog@mail.gmail.com>
Date: Sun, 29 Jun 2025 21:19:36 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: Hans de Goede <hansg@...nel.org>, LiangCheng Wang <zaq14760@...il.com>, mchehab@...nel.org,
sakari.ailus@...ux.intel.com, andy@...nel.org, gregkh@...uxfoundation.org,
nathan@...nel.org, nick.desaulniers+lkml@...il.com, morbo@...gle.com,
justinstitt@...gle.com, linux-media@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-staging@...ts.linux.dev,
llvm@...ts.linux.dev
Subject: Re: [PATCH v7] staging: media: atomisp: code style cleanup series
On Sun, Jun 29, 2025 at 9:13 PM Andy Shevchenko
<andy.shevchenko@...il.com> wrote:
>
> Yeah, that what I was afraid of. I don't know clang-format well
> enough, but it might be that tweaking existing .clang-format in the
> kernel can give something better.
Yeah, there are some proposed changes for the config that I have in
the backlog, and with a minimum upgrade we can also improve it further
(some things just couldn't be done well with the options that were
available at the time when I introduced it). That is why, at least so
far, clang-format worked best for formatting snippets or for new
files.
Cheers,
Miguel
Powered by blists - more mailing lists