From: Vasileios Amoiridis <vassilisamir@gmail.com>
To: dan.carpenter@linaro.org, jic23@kernel.org
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Vasileios Amoiridis <vassilisamir@gmail.com>
Subject: [PATCH v1 0/1] iio: chemical: bme680: resolve issue reported by
Date: Thu, 31 Oct 2024 00:54:23 +0100 [thread overview]
Message-ID: <20241030235424.214935-1-vassilisamir@gmail.com> (raw)
According to Dan [1], the previous approach was prone to endianness and
variable initialization issues because of the typecasting of a s32 to
s16 variable. Fix this, by using a local variable and not reusing the
local ones.
[1]: https://lore.kernel.org/linux-iio/13f764f7-4cc4-4563-81f6-0393732729a6@stanley.mountain/
Vasileios Amoiridis (1):
iio: chemical: bme680: use s16 variable for temp value to avoid
casting
drivers/iio/chemical/bme680_core.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--
2.43.0
next reply other threads:[~2024-10-30 23:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 23:54 Vasileios Amoiridis [this message]
2024-10-30 23:54 ` [PATCH v1] iio: chemical: bme680: use s16 variable for temp value to avoid casting Vasileios Amoiridis
2024-10-31 19:22 ` 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=20241030235424.214935-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
all inboxes | Powered by JetHome®