Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, u.kleine-koenig@baylibre.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.10.y 1/3] rtc: Improve performance of rtc_time64_to_tm(). Add tests.
Date: Wed, 11 Jun 2025 09:24:36 -0400	[thread overview]
Message-ID: <20250610175140-9e8c5ce35d7b59ba@stable.kernel.org> (raw)
In-Reply-To: <b301ceb67e1ab9fd522e17433540de464aec2c0b.1749539184.git.u.kleine-koenig@baylibre.com>

[ Sasha's backport helper bot ]

Hi,

Summary of potential issues:
⚠️ Found follow-up fixes in mainline

The upstream commit SHA1 provided is correct: 1d1bb12a8b1805ddeef9793ebeb920179fb0fa38

WARNING: Author mismatch between patch and upstream commit:
Backport author: <u.kleine-koenig@baylibre.com>
Commit author: Cassio Neri<cassio.neri@gmail.com>

Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.14.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (exact SHA1)
6.1.y | Present (exact SHA1)
5.15.y | Present (exact SHA1)

Found fixes commits:
8a904a3caa88 rtc: test: Fix invalid format specifier.

Note: The patch differs from the upstream commit:
---
1:  1d1bb12a8b180 ! 1:  b0856f15968b7 rtc: Improve performance of rtc_time64_to_tm(). Add tests.
    @@ Metadata
      ## Commit message ##
         rtc: Improve performance of rtc_time64_to_tm(). Add tests.
     
    +    commit 1d1bb12a8b1805ddeef9793ebeb920179fb0fa38 upstream.
    +
         The current implementation of rtc_time64_to_tm() contains unnecessary
         loops, branches and look-up tables. The new one uses an arithmetic-based
         algorithm appeared in [1] and is approximately 4.3 times faster (YMMV).
    @@ Commit message
         Reported-by: kernel test robot <lkp@intel.com>
         Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
         Link: https://lore.kernel.org/r/20210624201343.85441-1-cassio.neri@gmail.com
    +    Signed-off-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>
     
      ## drivers/rtc/Kconfig ##
     @@ drivers/rtc/Kconfig: config RTC_MC146818_LIB
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.10.y       |  Success    |  Success   |

  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 [this message]
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

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=20250610175140-9e8c5ce35d7b59ba@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