mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] sched/urgent for v6.16-rc5
Date: Sun, 6 Jul 2025 10:30:33 +0200	[thread overview]
Message-ID: <20250706083033.GAaGo0KbMDFzyQQLmR@fat_crate.local> (raw)

Hi Linus,

please pull the sched/urgent lineup for v6.16-rc5.

Thx.

---

The following changes since commit d0b3b7b22dfa1f4b515fd3a295b3fd958f9e81af:

  Linux 6.16-rc4 (2025-06-29 13:09:04 -0700)

are available in the Git repository at:

  ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/tip/tip tags/sched_urgent_for_v6.16_rc5

for you to fetch changes up to fc975cfb36393db1db517fbbe366e550bcdcff14:

  sched/deadline: Fix dl_server runtime calculation formula (2025-07-04 10:35:56 +0200)

----------------------------------------------------------------
- Fix the calculation of the deadline server task's runtime as this mishap was
  preventing realtime tasks from running

- Avoid a race condition during migrate-swapping two tasks

- Fix the string reported for the "none" dynamic preemption option

----------------------------------------------------------------
Peter Zijlstra (1):
      sched/core: Fix migrate_swap() vs. hotplug

Thomas Weißschuh (1):
      sched: Fix preemption string of preempt_dynamic_none

kuyo chang (1):
      sched/deadline: Fix dl_server runtime calculation formula

 kernel/sched/core.c     |  7 ++++++-
 kernel/sched/deadline.c | 10 +++++-----
 kernel/stop_machine.c   | 20 ++++++++++----------
 3 files changed, 21 insertions(+), 16 deletions(-)


-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

             reply	other threads:[~2025-07-06  8:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-06  8:30 Borislav Petkov [this message]
2025-07-06 19:03 ` pr-tracker-bot

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=20250706083033.GAaGo0KbMDFzyQQLmR@fat_crate.local \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@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

all inboxes | Powered by JetHome®