From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Vasileios Amoiridis <vassilisamir@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>, <lars@metafoo.de>,
<andriy.shevchenko@linux.intel.com>, <ang.iglesiasg@gmail.com>,
<mazziesaccount@gmail.com>, <ak@it-klinger.de>,
<petre.rodan@subdimension.ro>, <phil@raspberrypi.com>,
<579lpy@gmail.com>, <u.kleine-koenig@pengutronix.de>,
<biju.das.jz@bp.renesas.com>, <linus.walleij@linaro.org>,
<semen.protsenko@linaro.org>, <linux-iio@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/6] iio: pressure: bmp280: Various driver cleanups
Date: Sun, 14 Apr 2024 19:13:22 +0100 [thread overview]
Message-ID: <20240414191322.00005408@Huawei.com> (raw)
In-Reply-To: <20240414161902.GA4388@vamoiridPC>
On Sun, 14 Apr 2024 18:19:02 +0200
Vasileios Amoiridis <vassilisamir@gmail.com> wrote:
> On Sat, Apr 13, 2024 at 05:52:57PM +0100, Jonathan Cameron wrote:
> > On Sun, 7 Apr 2024 19:29:15 +0200
> > Vasileios Amoiridis <vassilisamir@gmail.com> wrote:
> >
> > > Various driver cleanups including:
> > >
> > Not sure how we got to a v4 with a patch title various.
> >
> > If you have to list multiple changes, it should normally
> > be multiple patches.
> >
> > White space can all be grouped, but the others should be separate.
> > Please break it up for v5.
> >
> > I'll take a look at the actual changes even though I won't merge
> > a 'various' patch like this.
> >
> > I may well miss things because there is simply too much in here
> > and some of the diffs are subtle as it can be hard to spot
> > if it's a name change or a functional change.
> >
>
> Hi Jonathan,
>
> Thank you once again for the very valuable feedback! We didn't actually
> reached v4 with a title various. It is just that the more that I was
> working on this driver the more things I noticed that could be cleaned
> (apparently not all of them as you mentioned) but still quite some that
> could be cleaned. So I took the opportunity before adding the triggered
> buffer support to do this cleaning.
>
> The reason that I did it in a big patch is that in a previous version
> of this set of patches, you mentioned that we must find a way to make
> the commits less, so that's why I thought that a cleaning patch could
> include many different types of cleaning since there are no functional
> changes but as I understand that's not the case, so I will split them
> for v5.
Ah. I was interested in reducing overhead of having the same change
that everyone was happy with being posted in lots of versions due
to other changes later in the series. Not reducing number
of patches overall!
BTW I picked up the header sorting in v3 so you don't need to
carry that change any more.
Jonathan
next prev parent reply other threads:[~2024-04-14 18:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-07 17:29 [PATCH v4 0/6] Driver cleanup and series to add triggered buffer Vasileios Amoiridis
2024-04-07 17:29 ` [PATCH v4 1/6] iio: pressure: bmp280: Various driver cleanups Vasileios Amoiridis
2024-04-13 16:52 ` Jonathan Cameron
2024-04-14 16:19 ` Vasileios Amoiridis
2024-04-14 18:13 ` Jonathan Cameron [this message]
2024-04-14 23:41 ` Vasileios Amoiridis
2024-04-07 17:29 ` [PATCH v4 2/6] iio: pressure: bmp280: Refactorize reading functions Vasileios Amoiridis
2024-04-13 16:56 ` Jonathan Cameron
2024-04-07 17:29 ` [PATCH v4 3/6] iio: pressure: bmp280: Introduce new cleanup routines Vasileios Amoiridis
2024-04-13 16:58 ` Jonathan Cameron
2024-04-07 17:29 ` [PATCH v4 4/6] iio: pressure: bmp280: Generalize read_{temp,press,humid}() functions Vasileios Amoiridis
2024-04-07 17:29 ` [PATCH v4 5/6] iio: pressure: bmp280: Add SCALE, RAW values in channels and refactorize them Vasileios Amoiridis
2024-04-07 17:29 ` [PATCH v4 6/6] iio: pressure: bmp280: Add triggered buffer support Vasileios Amoiridis
2024-04-13 17:06 ` Jonathan Cameron
2024-04-07 21:51 ` [PATCH v4 0/6] Driver cleanup and series to add triggered buffer Angel Iglesias
2024-04-08 15:01 ` Andy Shevchenko
2024-04-08 16:58 ` Vasileios Amoiridis
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=20240414191322.00005408@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=579lpy@gmail.com \
--cc=ak@it-klinger.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ang.iglesiasg@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=petre.rodan@subdimension.ro \
--cc=phil@raspberrypi.com \
--cc=semen.protsenko@linaro.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vassilisamir@gmail.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