[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAATBrPEMuoVQwCqycrZ14PsNH4u+Di+eycAofObb=8kS9dpvfQ@mail.gmail.com>
Date: Thu, 4 Sep 2025 13:43:15 +0200
From: 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: [RFC PATCH v2 1/2] staging: media: atomisp: Change name to better
follow its behavior
Hi Andy
Regardless commit message, is the change OK and can post it as a
patch, or similarly to second patch it is not worth the effort as it
will be refactored at some point?
> Change name to clearly states what function does.
Proposed description:
staging: media: atomisp: Rename `inv_subword()` to `clear_subword()`
Function `inv_subword()` does not inverse bits or subword and neither is
inverse operation for `subword()` function. It is used to clear target bits of
move_subword operation (specified by start and end-1 indexes). Name
`clear_subword()` explains the function behavior better.
Best Regards
Adrian Barnaś
On Thu, Sep 4, 2025 at 9:48 AM Andy Shevchenko
<andriy.shevchenko@...el.com> wrote:
>
> On Wed, Sep 03, 2025 at 09:27:53AM +0000, Adrian Barnaś wrote:
> > Change name to clearly states what function does.
>
> The Subject and the body of the commit message should be more specific.
>
> Missing blank line.
>
> > Signed-off-by: Adrian Barnaś <abarnas@...gle.com>
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
Powered by blists - more mailing lists