From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, sean@geanix.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y] iio: accel: fxls8962af: Fix temperature calculation
Date: Sat, 21 Jun 2025 04:52:18 -0400 [thread overview]
Message-ID: <20250620234127-364b21949ff5b59b@stable.kernel.org> (raw)
In-Reply-To: <20250620101904.10740-1-sean@geanix.com>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
⚠️ Found matching upstream commit but patch is missing proper reference to it
Found matching upstream commit: 16038474e3a0263572f36326ef85057aaf341814
Status in newer kernel trees:
6.15.y | Present (different SHA1: b0df531da1ef)
6.12.y | Not found
6.6.y | Not found
Note: The patch differs from the upstream commit:
---
1: 16038474e3a02 ! 1: 08702bd93754a iio: accel: fxls8962af: Fix temperature calculation
@@ Commit message
Signed-off-by: Sean Nyekjaer <sean@geanix.com>
Link: https://patch.msgid.link/20250505-fxls-v4-1-a38652e21738@geanix.com
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
+ (cherry picked from commit 16038474e3a0263572f36326ef85057aaf341814)
## drivers/iio/accel/fxls8962af-core.c ##
@@
+ #include <linux/pm_runtime.h>
#include <linux/regulator/consumer.h>
#include <linux/regmap.h>
- #include <linux/types.h>
+#include <linux/units.h>
#include <linux/iio/buffer.h>
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
prev parent reply other threads:[~2025-06-21 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 9:34 FAILED: patch "[PATCH] iio: accel: fxls8962af: Fix temperature calculation" failed to apply to 6.1-stable tree gregkh
2025-06-20 10:19 ` [PATCH 6.1.y] iio: accel: fxls8962af: Fix temperature calculation Sean Nyekjaer
2025-06-21 8:52 ` Sasha Levin [this message]
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=20250620234127-364b21949ff5b59b@stable.kernel.org \
--to=sashal@kernel.org \
--cc=sean@geanix.com \
--cc=stable@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.