The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Anna-Maria Behnsen <anna-maria@linutronix.de>,
	Frederic Weisbecker <frederic@kernel.org>
Subject: [GIT PULL] timer subsystem fixes
Date: Sun, 7 Jun 2026 07:07:50 +0200	[thread overview]
Message-ID: <aiT8pgOM0LCF8D15@gmail.com> (raw)

Linus,

Please pull the latest timers/urgent Git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-urgent-2026-06-07

for you to fetch changes up to d486b4934a8e504376b85cdb3766f306d57aff5b:

Miscellaneous timer fixes:

 - Fix the arch_inlined_clockevent_set_next_coupled() prototype
   in the !CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST case
   (Naveen Kumar Chaudhary)

 - Fix an off-by-1 bug in the sys_settimeofday() usecs validation
   code (Naveen Kumar Chaudhary)

 - Mark vdso_k_*_data pointers as __ro_after_init
   (Thomas Weißschuh)

 - Fix livelock race in tmigr_handle_remote_up()
   (Amit Matityahu)

 Thanks,

	Ingo

------------------>
Amit Matityahu (1):
      timers/migration: Fix livelock in tmigr_handle_remote_up()

Naveen Kumar Chaudhary (2):
      clockevents: Fix duplicate type specifier in stub function parameter
      time: Fix off-by-one in settimeofday() usec validation

Thomas Weißschuh (1):
      vdso/datastore: Mark vdso_k_*_data pointers as __ro_after_init


 kernel/time/clockevents.c     | 2 +-
 kernel/time/time.c            | 2 +-
 kernel/time/timer_migration.c | 8 ++++++--
 lib/vdso/datastore.c          | 6 +++---
 4 files changed, 11 insertions(+), 7 deletions(-)

             reply	other threads:[~2026-06-07  5:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-07  5:07 Ingo Molnar [this message]
2026-06-07 20:43 ` [GIT PULL] timer subsystem fixes pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2026-01-24  9:38 Ingo Molnar
2026-01-24 18:00 ` pr-tracker-bot
2025-11-23  7:58 Ingo Molnar
2025-11-23 16:26 ` pr-tracker-bot
2025-05-11  7:49 Ingo Molnar
2025-05-11 18:40 ` pr-tracker-bot
2025-05-04  7:26 Ingo Molnar
2025-05-04  7:34 ` Ingo Molnar

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=aiT8pgOM0LCF8D15@gmail.com \
    --to=mingo@kernel.org \
    --cc=anna-maria@linutronix.de \
    --cc=daniel.lezcano@linaro.org \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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