From: Nikita Travkin <nikita@trvn.ru>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-iio@vger.kernel.org, Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
kernel@pengutronix.de
Subject: Re: [PATCH v2 0/4] fix regmap, initialization of ltr559, endianness and mark structs as const
Date: Fri, 11 Jun 2021 00:20:35 +0500 [thread overview]
Message-ID: <5d237fb56774540fc525109d8e850782@trvn.ru> (raw)
In-Reply-To: <20210610134619.2101372-1-mkl@pengutronix.de>
Marc Kleine-Budde писал 10.06.2021 18:46:
> Hello,
>
> here are 3 bug-fixes (probably stable material) and 1 enhancement for
> the ltr501 driver.
>
> regards,
> Marc
>
> changes since v1:
> - all: add Andy Shevchenko's Reviewed-by
> - 3/4: move endianness conversion to the callee
Hi,
Tested this series on Wileyfox Swift (Longcheer L8150) with ltr559,
it works nicely now, thank you!
Tested-by: Nikita Travkin <nikita@trvn.ru> # ltr559
--
regards,
Nikita
next prev parent reply other threads:[~2021-06-10 19:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 13:46 [PATCH v2 0/4] fix regmap, initialization of ltr559, endianness and mark structs as const Marc Kleine-Budde
2021-06-10 13:46 ` [PATCH v2 1/4] iio: ltr501: mark register holding upper 8 bits of ALS_DATA{0,1} and PS_DATA as volatile, too Marc Kleine-Budde
2021-06-10 13:46 ` [PATCH v2 2/4] iio: ltr501: ltr559: fix initialization of LTR501_ALS_CONTR Marc Kleine-Budde
2021-06-10 13:46 ` [PATCH v2 3/4] iio: ltr501: ltr501_read_ps(): add missing endianness conversion Marc Kleine-Budde
2021-06-10 13:46 ` [PATCH v2 4/4] iio: ltr501: mark ltr501_chip_info as const Marc Kleine-Budde
2021-06-10 19:20 ` Nikita Travkin [this message]
2021-06-11 17:44 ` [PATCH v2 0/4] fix regmap, initialization of ltr559, endianness and mark structs " 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=5d237fb56774540fc525109d8e850782@trvn.ru \
--to=nikita@trvn.ru \
--cc=jic23@kernel.org \
--cc=kernel@pengutronix.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=mkl@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.