From: Thomas Gleixner <tglx@linutronix.de>
To: stable@vger.kernel.org, stable-commits@vger.kernel.org
Cc: John Stultz <jstultz@google.com>, Stephen Boyd <sboyd@kernel.org>,
Richard Cochran <richardcochran@gmail.com>
Subject: Re: Patch "ntp: Introduce struct ntp_data" has been added to the 6.1-stable tree
Date: Mon, 09 Dec 2024 13:12:13 +0100 [thread overview]
Message-ID: <87ttbdoy1u.ffs@tglx> (raw)
In-Reply-To: <20241209113201.3171845-1-sashal@kernel.org>
On Mon, Dec 09 2024 at 06:32, Sasha Levin wrote:
> This is a note to let you know that I've just added the patch titled
> commit 57103d282a874ed716f489b7b336b8d833ba43b2
> Author: Thomas Gleixner <tglx@linutronix.de>
> Date: Wed Sep 11 15:17:43 2024 +0200
>
> ntp: Introduce struct ntp_data
>
> [ Upstream commit 68f66f97c5689825012877f58df65964056d4b5d ]
>
> All NTP data is held in static variables. That prevents the NTP code from
> being reuasble for non-system time timekeepers, e.g. per PTP clock
> timekeeping.
>
> Introduce struct ntp_data and move tick_usec into it for a start.
>
> No functional change.
>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Signed-off-by: Anna-Maria Behnsen <anna-maria@linutronix.de>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Acked-by: John Stultz <jstultz@google.com>
> Link: https://lore.kernel.org/all/20240911-devel-anna-maria-b4-timers-ptp-ntp-v1-7-2d52f4e13476@linutronix.de
> Stable-dep-of: f5807b0606da ("ntp: Remove invalid cast in time offset math")
I sent a backport of this change, which is a one liner:
https://lore.kernel.org/stable/878qssr16f.ffs@tglx/
There is no point to backport the whole data struct change series for
that.
Thanks,
tglx
next parent reply other threads:[~2024-12-09 12:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241209113201.3171845-1-sashal@kernel.org>
2024-12-09 12:12 ` Thomas Gleixner [this message]
2024-12-09 13:07 ` Patch "ntp: Introduce struct ntp_data" has been added to the 6.1-stable tree Greg KH
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=87ttbdoy1u.ffs@tglx \
--to=tglx@linutronix.de \
--cc=jstultz@google.com \
--cc=richardcochran@gmail.com \
--cc=sboyd@kernel.org \
--cc=stable-commits@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox