From: Vasileios Amoiridis <vassilisamir@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Vasileios Amoiridis <vassilisamir@gmail.com>,
lars@metafoo.de, ang.iglesiasg@gmail.com,
andriy.shevchenko@linux.intel.com, linus.walleij@linaro.org,
semen.protsenko@linaro.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] drivers: iio: pressure: Sort headers of BMPxxx SPI driver
Date: Sat, 24 Feb 2024 23:09:44 +0100 [thread overview]
Message-ID: <20240224220944.GA105280@vamoiridPC> (raw)
In-Reply-To: <20240224180412.0b23a105@jic23-huawei>
On Sat, Feb 24, 2024 at 06:04:12PM +0000, Jonathan Cameron wrote:
> On Tue, 20 Feb 2024 23:43:28 +0100
> Vasileios Amoiridis <vassilisamir@gmail.com> wrote:
>
> > Alphabetical sorting and separation of headers for the BMPxxx
> > SPI driver.
> >
> > Signed-off-by: Vasileios Amoiridis <vassilisamir@gmail.com>
>
> Hi Vasileios,
>
> No. This ends up as a dependency of the fix which will want backporting.
> This would make it a non minimal change. As such the reordering comes
> after the other patch (and not until it is upstream).
>
> All that needed to happen was bits.h being first of the includes in the
> fixes patch so that a sort later was minimal. Doing that had no impact
> on the complexity of the fix to backport so was just good code hygiene
> in that would simplify the resort to follow.
>
> Anyhow, dropping this for now. Please send an update version
> next cycle once the fix is upstream
>
> Thanks,
>
> Jonathan
>
Hi Jonathan,
Thank you very much again for the comments and I am sorry for not versioning
them properly, it won't happen again. I also understand what you mean in the
previous message and I will definitely submit it again, first thing after the
changes are upstreamed.
Thanks,
Vasileios
> > ---
> > drivers/iio/pressure/bmp280-spi.c | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/iio/pressure/bmp280-spi.c b/drivers/iio/pressure/bmp280-spi.c
> > index e8a5fed07e88..fd7ec6a5bca3 100644
> > --- a/drivers/iio/pressure/bmp280-spi.c
> > +++ b/drivers/iio/pressure/bmp280-spi.c
> > @@ -4,11 +4,12 @@
> > *
> > * Inspired by the older BMP085 driver drivers/misc/bmp085-spi.c
> > */
> > -#include <linux/module.h>
> > -#include <linux/spi/spi.h>
> > #include <linux/err.h>
> > +#include <linux/module.h>
> > #include <linux/regmap.h>
> >
> > +#include <linux/spi/spi.h>
> > +
> > #include "bmp280.h"
> >
> > static int bmp280_regmap_spi_write(void *context, const void *data,
>
prev parent reply other threads:[~2024-02-24 22:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 22:43 [PATCH 1/2] drivers: iio: pressure: Sort headers of BMPxxx SPI driver Vasileios Amoiridis
2024-02-20 22:43 ` [PATCH 2/2] drivers: iio: pressure: Fixes BMP38x and BMP390 SPI support Vasileios Amoiridis
2024-02-21 13:21 ` Andy Shevchenko
2024-02-24 18:01 ` Jonathan Cameron
2024-02-22 7:58 ` Angel Iglesias
2024-02-21 13:20 ` [PATCH 1/2] drivers: iio: pressure: Sort headers of BMPxxx SPI driver Andy Shevchenko
2024-02-22 7:54 ` Angel Iglesias
2024-02-24 18:04 ` Jonathan Cameron
2024-02-24 22:09 ` Vasileios Amoiridis [this message]
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=20240224220944.GA105280@vamoiridPC \
--to=vassilisamir@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ang.iglesiasg@gmail.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=semen.protsenko@linaro.org \
/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