From: Alejandro Tafalla <atafalla@dnyon.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Lorenzo Bianconi <lorenzo@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] iio: imu: lsm6dsx: Fix mount matrix retrieval
Date: Mon, 17 Jul 2023 23:17:10 +0200 [thread overview]
Message-ID: <3017278.mvXUDI8C0e@alexpc> (raw)
In-Reply-To: <20230715183515.56deaa1d@jic23-huawei>
On sábado, 15 de julio de 2023 19:35:15 (CEST) Jonathan Cameron wrote:
> On Fri, 14 Jul 2023 17:31:26 +0200
>
> Alejandro Tafalla <atafalla@dnyon.com> wrote:
> > The function lsm6dsx_get_acpi_mount_matrix should return an error when
> > ACPI
> > support is not enabled to allow executing iio_read_mount_matrix in the
> > probe function.
> >
> > Fixes: dc3d25f22b88 ("iio: imu: lsm6dsx: Add ACPI mount matrix retrieval")
>
> I can fix it up whilst applying if no other issues, but there must not be
> a blank line here. All tags need to be in a single block for some tooling
> that is used with the kernel tree (and some of the checking scripts warn
> about this so it won't get applied with the blank line here).
Okay, i'll keep it in mind for new patches. Thank you.
>
> > Signed-off-by: Alejandro Tafalla <atafalla@dnyon.com>
> > ---
> > Changes in v3:
> > - Removed unneeded check for err == -EOPNOTSUPP.
> >
> > Changes in v2:
> > - Use of error codes instead of true/false
> >
> > drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c
> > b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c index
> > 6a18b363cf73..b6e6b1df8a61 100644
> > --- a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c
> > +++ b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c
> > @@ -2687,7 +2687,7 @@ static int lsm6dsx_get_acpi_mount_matrix(struct
> > device *dev,>
> > static int lsm6dsx_get_acpi_mount_matrix(struct device *dev,
> >
> > struct
iio_mount_matrix *orientation)
> >
> > {
> >
> > - return false;
> > + return -EOPNOTSUPP;
> >
> > }
> >
> > #endif
next prev parent reply other threads:[~2023-07-17 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 15:31 [PATCH v3] iio: imu: lsm6dsx: Fix mount matrix retrieval Alejandro Tafalla
2023-07-15 17:35 ` Jonathan Cameron
2023-07-17 21:17 ` Alejandro Tafalla [this message]
2023-07-20 18:40 ` Jonathan Cameron
2023-07-20 21:27 ` Lorenzo Bianconi
2023-07-23 12:50 ` Jonathan Cameron
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=3017278.mvXUDI8C0e@alexpc \
--to=atafalla@dnyon.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@kernel.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