From: Vasileios Amoiridis <vassilisamir@gmail.com>
To: jic23@kernel.org
Cc: dan.carpenter@linaro.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org,
Vasileios Amoiridis <vassilisamir@gmail.com>
Subject: [PATCH v3 0/2] pressure: bmp280: Improve pushing of data to buffer
Date: Mon, 30 Sep 2024 22:23:51 +0200 [thread overview]
Message-ID: <20240930202353.38203-1-vassilisamir@gmail.com> (raw)
Changes in v3:
[PATCH v3 1/2]:
- Remove fixes tag
[PATCH v3 2/2]:
- Use internal s32 *chans variable to better visualize what is
taking place in the data->sensor_data.
- Use proper size/alignment to the data->sensor_data.
P.S. After this patchseries is applied, I will rebase this [1] and resend it.
[1]: https://lore.kernel.org/linux-iio/20240914002900.45158-1-vassilisamir@gmail.com/
---
v2: https://lore.kernel.org/linux-iio/20240929112511.100292-1-vassilisamir@gmail.com/
v1: https://lore.kernel.org/linux-iio/20240823172017.9028-1-vassilisamir@gmail.com/
Vasileios Amoiridis (2):
iio: pressure: bmp280: Use unsigned type for raw values
iio: pressure: bmp280: Use char instead of s32 for data buffer
drivers/iio/pressure/bmp280-core.c | 69 +++++++++++++++++++-----------
drivers/iio/pressure/bmp280.h | 4 +-
2 files changed, 46 insertions(+), 27 deletions(-)
--
2.25.1
next reply other threads:[~2024-09-30 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 20:23 Vasileios Amoiridis [this message]
2024-09-30 20:23 ` [PATCH v3 1/2] iio: pressure: bmp280: Use unsigned type for raw values Vasileios Amoiridis
2024-09-30 20:23 ` [PATCH v3 2/2] iio: pressure: bmp280: Use char instead of s32 for data buffer Vasileios Amoiridis
2024-10-11 18:59 ` Kees Bakker
2024-10-06 14:05 ` [PATCH v3 0/2] pressure: bmp280: Improve pushing of data to buffer Jonathan Cameron
2024-10-07 19:35 ` 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=20240930202353.38203-1-vassilisamir@gmail.com \
--to=vassilisamir@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).