From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Atharva Tiwari <evepolonium@gmail.com>,
kernel test robot <lkp@intel.com>,
Jean Delvare <jdelvare@suse.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: amd756: Fix endianness handling for word data
Date: Sat, 4 Jan 2025 11:32:59 +0100 [thread overview]
Message-ID: <Z3kOW11SxEVwqcw-@ninjato> (raw)
In-Reply-To: <eqjgc5a4fiz6csqmehyo66yduorxt3d3vnr62d5ijxy3wooheo@qabiaft2nri3>
[-- Attachment #1: Type: text/plain, Size: 403 bytes --]
> Yeah! That was my first thought, but because this was reported
> by LKP (which I respect more than other code analyzers) as a
> potential issue, I was on the 50-50.
A potential issue on outdated hardware (or better: non-existing versions
of outdated harware) which has not showed up since the git era is not
really a for-current bugfix in my book. That being said, it does not
harm in for-current.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-01-04 10:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 10:34 [PATCH] i2c: amd756: Fix endianness handling for word data Atharva Tiwari
2025-01-03 23:18 ` Andi Shyti
2025-01-03 23:28 ` Wolfram Sang
2025-01-03 23:50 ` Andi Shyti
2025-01-04 10:32 ` Wolfram Sang [this message]
2025-01-07 18:57 ` Andi Shyti
2025-01-09 9:23 ` Wolfram Sang
2025-01-03 23:32 ` Andi Shyti
2025-01-04 3:46 ` Andi Shyti
-- strict thread matches above, loose matches on Subject: below --
2024-12-27 13:22 Atharva Tiwari
2024-12-30 2:03 ` Andi Shyti
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=Z3kOW11SxEVwqcw-@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=andi.shyti@kernel.org \
--cc=evepolonium@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
/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