Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, stable-commits@vger.kernel.org
Cc: John Stultz <jstultz@google.com>,
	Thomas Gleixner <tglx@kernel.org>,
	Stephen Boyd <sboyd@kernel.org>,
	Miroslav Lichvar <mlichvar@redhat.com>,
	Anna-Maria Gleixner <anna-maria@linutronix.de>,
	Frederic Weisbecker <frederic@kernel.org>,
	Ingo Molnar <mingo@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: Patch "timekeeping: add CONFIG_LEGACY_TIMER_TICK" has been added to the 5.10-stable tree
Date: Tue, 17 Nov 2026 19:23:09 -0500	[thread overview]
Message-ID: <2026-11-17-1-daily-reply-0010@kernel.org> (raw)
Message-ID: <20261118002309.3IfESL_PYCJvWWGLWcYeP8Mt1TzE2Qgxdiynp-nfDwI@z> (raw)
In-Reply-To: <101777e2-a6fe-4d1a-9a9e-7179ce89bd65@app.fastmail.com>

> I don't see how this is a dependency of 2927f7ca7844, it looks
> unrelated to me, and the patch only adds an unused function.

You are right, it is not a functional dependency of 2927f7ca7844 ("time:
Prevent time64_to_tm() day truncation on 32-bit"). The next patch queued for
5.10, de995239ab01 ("time: Improve performance of time64_to_tm()"), has the
LEGACY_TIMER_TICK Kconfig entry as context in its kernel/time/Kconfig hunk, so
I took it to keep the later patches unmodified. It only adds an unused function
on 5.10.

-- 
Thanks,
Sasha

      reply	other threads:[~2026-11-18  0:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20261117200127.2399332-1-sashal@kernel.org>
2026-11-17 20:15 ` Patch "timekeeping: add CONFIG_LEGACY_TIMER_TICK" has been added to the 5.10-stable tree Arnd Bergmann
     [not found]   ` <20261118002309.3IfESL_PYCJvWWGLWcYeP8Mt1TzE2Qgxdiynp-nfDwI@z>
2026-11-18  0:23     ` 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=2026-11-17-1-daily-reply-0010@kernel.org \
    --to=sashal@kernel.org \
    --cc=anna-maria@linutronix.de \
    --cc=arnd@arndb.de \
    --cc=frederic@kernel.org \
    --cc=jstultz@google.com \
    --cc=mingo@kernel.org \
    --cc=mlichvar@redhat.com \
    --cc=sboyd@kernel.org \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@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