All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.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 v5.15-rc4
Date: Sun, 3 Oct 2021 12:27:37 +0200	[thread overview]
Message-ID: <YVmFmV/BDpXrn/yw@zn.tnic> (raw)

Hi Linus,

please pull three urgent fixes to scheduler land, for v5.15.

Thx.

---

The following changes since commit e4e737bb5c170df6135a127739a9e6148ee3da82:

  Linux 5.15-rc2 (2021-09-19 17:28:22 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/sched_urgent_for_v5.15_rc4

for you to fetch changes up to 83d40a61046f73103b4e5d8f1310261487ff63b0:

  sched: Always inline is_percpu_thread() (2021-10-01 13:57:57 +0200)

----------------------------------------------------------------
- Tell the compiler to always inline is_percpu_thread()

- Make sure tunable_scaling buffer is null-terminated after an update in sysfs

- Fix LTP named regression due to cgroup list ordering

----------------------------------------------------------------
Mel Gorman (1):
      sched/fair: Null terminate buffer when updating tunable_scaling

Michal Koutný (1):
      sched/fair: Add ancestors of unthrottled undecayed cfs_rq

Peter Zijlstra (1):
      sched: Always inline is_percpu_thread()

 include/linux/sched.h | 2 +-
 kernel/sched/debug.c  | 8 +++++++-
 kernel/sched/fair.c   | 6 +++++-
 3 files changed, 13 insertions(+), 3 deletions(-)

-- 
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg

             reply	other threads:[~2021-10-03 10:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-03 10:27 Borislav Petkov [this message]
2021-10-03 18:20 ` [GIT PULL] sched/urgent for v5.15-rc4 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=YVmFmV/BDpXrn/yw@zn.tnic \
    --to=bp@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.