From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Sasha Levin" <sashal@kernel.org>
Subject: Re: [PATCH 5.10.y 3/3] rtc: Fix offset calculation for .start_secs < 0
Date: Wed, 11 Jun 2025 09:24:32 -0400 [thread overview]
Message-ID: <20250610180120-50d991767c9b46a7@stable.kernel.org> (raw)
In-Reply-To: <1f965f4886f65e45423f863930ccc7139944272d.1749539184.git.u.kleine-koenig@baylibre.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: fe9f5f96cfe8b82d0f24cbfa93718925560f4f8d
WARNING: Author mismatch between patch and upstream commit:
Backport author: <u.kleine-koenig@baylibre.com>
Commit author: Alexandre Mergnat<amergnat@baylibre.com>
Status in newer kernel trees:
6.15.y | Present (different SHA1: cea549ca705b)
6.14.y | Present (different SHA1: 57082e0300d5)
6.12.y | Present (different SHA1: 6b482b16f32e)
6.6.y | Present (different SHA1: 3d8efdcbc6ce)
6.1.y | Present (different SHA1: b2677da58ed4)
5.15.y | Present (different SHA1: 0931dc7be5dd)
Note: The patch differs from the upstream commit:
---
1: fe9f5f96cfe8b ! 1: 8aa260951391e rtc: Fix offset calculation for .start_secs < 0
@@ Metadata
## Commit message ##
rtc: Fix offset calculation for .start_secs < 0
+ commit fe9f5f96cfe8b82d0f24cbfa93718925560f4f8d upstream.
+
The comparison
rtc->start_secs > rtc->range_max
@@ Commit message
Reviewed-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>
Link: https://lore.kernel.org/r/20250428-enable-rtc-v4-2-2b2f7e3f9349@baylibre.com
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
+ Signed-off-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>
## drivers/rtc/class.c ##
@@ drivers/rtc/class.c: static void rtc_device_get_offset(struct rtc_device *rtc)
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y | Success | Success |
prev parent reply other threads:[~2025-06-11 13:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 7:34 [PATCH 5.10.y 0/3] rtc: backport support for handling dates before 1970 Uwe Kleine-König
2025-06-10 7:34 ` [PATCH 5.10.y 1/3] rtc: Improve performance of rtc_time64_to_tm(). Add tests Uwe Kleine-König
2025-06-11 13:24 ` Sasha Levin
2025-06-10 7:34 ` [PATCH 5.10.y 2/3] rtc: Make rtc_time64_to_tm() support dates before 1970 Uwe Kleine-König
2025-06-10 20:33 ` Cassio Neri
[not found] ` <CAOfgUPg0Z6e5+awuqVMa7QUPiJ7aPp-dX6QNk80Y-bhpBYcsoQ@mail.gmail.com>
2025-06-11 6:08 ` Uwe Kleine-König
2025-06-11 7:33 ` Alexandre Belloni
2025-06-11 18:32 ` Cassio Neri
2025-06-11 13:16 ` Sasha Levin
2025-06-10 7:35 ` [PATCH 5.10.y 3/3] rtc: Fix offset calculation for .start_secs < 0 Uwe Kleine-König
2025-06-11 13:24 ` 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=20250610180120-50d991767c9b46a7@stable.kernel.org \
--to=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=u.kleine-koenig@baylibre.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