From: Ulrich Hecht <uli@fpond.eu>
To: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"pavel@nabladev.com" <pavel@nabladev.com>,
"nobuhiro.iwamatsu.x90@mail.toshiba"
<nobuhiro.iwamatsu.x90@mail.toshiba>
Subject: Request for review for 4.19-st17, 4.19-cip133
Date: Thu, 21 May 2026 11:49:41 +0200 (CEST) [thread overview]
Message-ID: <516262162.225768.1779356981051@webmail.strato.de> (raw)
Hi!
Here are the manual backports for the upcoming 4.19 kernel release. As always they can be found in https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-st-rc
b7885f23ff4c9 x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2's op cache
da51b237e7bbd x86/CPU/AMD: Add X86_FEATURE_ZEN1
e49d8098895b4 x86/CPU/AMD: Rename init_amd_zn() to init_amd_zen_common()
f7c75253044df x86/CPU/AMD: Add ZenX generations flags
874e7cb1436fc ptrace: slightly saner 'get_dumpable()' logic
Thank you!
CU
Uli
next reply other threads:[~2026-05-21 9:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 9:49 Ulrich Hecht [this message]
2026-05-25 9:52 ` Request for review for 4.19-st17, 4.19-cip133 Pavel Machek
2026-05-26 2:02 ` [cip-dev] " nobuhiro.iwamatsu.x90
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=516262162.225768.1779356981051@webmail.strato.de \
--to=uli@fpond.eu \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro.iwamatsu.x90@mail.toshiba \
--cc=pavel@nabladev.com \
/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