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.17-rc2
Date: Sun, 30 Jan 2022 12:05:02 +0100 [thread overview]
Message-ID: <YfZw3s6XOmj9rtq1@zn.tnic> (raw)
Hi Linus,
please pull a single urgent scheduler fix for 5.17.
Thx.
---
The following changes since commit 0e3872499de1a1230cef5221607d71aa09264bd5:
kernel/sched: Remove dl_boosted flag comment (2022-01-18 12:10:00 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/sched_urgent_for_v5.17_rc2_p2
for you to fetch changes up to 809232619f5b15e31fb3563985e705454f32621f:
sched/membarrier: Fix membarrier-rseq fence command missing from query bitmask (2022-01-25 22:30:25 +0100)
----------------------------------------------------------------
- Make sure the membarrier-rseq fence commands are part of the reported
set when querying membarrier(2) commands through MEMBARRIER_CMD_QUERY
----------------------------------------------------------------
Mathieu Desnoyers (1):
sched/membarrier: Fix membarrier-rseq fence command missing from query bitmask
kernel/sched/membarrier.c | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg
next reply other threads:[~2022-01-30 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 11:05 Borislav Petkov [this message]
2022-01-30 11:10 ` [GIT PULL] sched/urgent for v5.17-rc2 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2022-01-23 11:06 Borislav Petkov
2022-01-23 15:47 ` 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=YfZw3s6XOmj9rtq1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox