[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aLW91kNOfi1ab6D3@smile.fi.intel.com>
Date: Mon, 1 Sep 2025 18:37:58 +0300
From: Andy Shevchenko <andriy.shevchenko@...el.com>
To: Adrian Barnaś <abarnas@...gle.com>
Cc: Hans de Goede <hansg@...nel.org>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
Andy Shevchenko <andy@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Dan Carpenter <dan.carpenter@...aro.org>,
linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-staging@...ts.linux.dev
Subject: Re: [PATCH 2/2] staging:media: atomisp: Whitespaces cleanup in vmem.c
On Mon, Sep 01, 2025 at 02:46:47PM +0200, Adrian Barnaś wrote:
> On Mon, Sep 1, 2025 at 2:23 PM Andy Shevchenko
> <andriy.shevchenko@...el.com> wrote:
> > On Mon, Sep 01, 2025 at 09:10:50AM +0000, Adrian Barnaś wrote:
> > > Whitespaces cleanup to conform with kernel style and improve readability.
> > Strange...
>
> You mean the commit description? Should I reword it?
No, the case I explained below.
> > Note, the style after the first patch is okay. I dunno what's wrong with it.
>
> Those were not violate the kernel code style indeed, but it looks more
> consistent this way for me.
> Should I revert those?
If you are talking about the second patch changes in the same functions, yes,
please, keep them untouched _after_ the patch 1.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists