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 v2 0/2]: pressure: bmp280: Improve pushing of data to buffer
Date: Sun, 29 Sep 2024 13:25:09 +0200 [thread overview]
Message-ID: <20240929112511.100292-1-vassilisamir@gmail.com> (raw)
Changes in v2:
- Add 1st commit with a small fix of some data types. Shouldn't pose a
problem.
- In commit no.2 add logic with "offset" to make it more clear what we
are adding in the buffer. Also move the memcpy() operations after the
if() statements so the memcpy happens only if the data are correct to
avoid overhead for no reason.
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/
---
v1: https://lore.kernel.org/linux-iio/20240823172017.9028-1-vassilisamir@gmail.com/
Vasileios Amoiridis (2):
iio: pressure: bmp280: Fix type for raw values
iio: pressure: bmp280: Use char instead of s32 for data buffer
drivers/iio/pressure/bmp280-core.c | 75 +++++++++++++++++++-----------
drivers/iio/pressure/bmp280.h | 5 +-
2 files changed, 51 insertions(+), 29 deletions(-)
--
2.25.1
next reply other threads:[~2024-09-29 11:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 11:25 Vasileios Amoiridis [this message]
2024-09-29 11:25 ` [PATCH v2 1/2] iio: pressure: bmp280: Fix type for raw values Vasileios Amoiridis
2024-09-29 17:04 ` Jonathan Cameron
2024-09-29 18:20 ` Vasileios Amoiridis
2024-09-29 11:25 ` [PATCH v2 2/2] iio: pressure: bmp280: Use char instead of s32 for data buffer Vasileios Amoiridis
2024-09-29 17:10 ` Jonathan Cameron
2024-09-29 18:26 ` Vasileios Amoiridis
2024-09-30 8:54 ` 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=20240929112511.100292-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 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.