CIP-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@nabladev.com>
To: Ulrich Hecht <uli@fpond.eu>
Cc: "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: Re: Request for review for 4.4-st77, 4.4-cip112
Date: Tue, 9 Jun 2026 10:51:13 +0200	[thread overview]
Message-ID: <aifUAaSVDIRHHN_a@duo.ucw.cz> (raw)
In-Reply-To: <1985872946.840508.1780932177008@webmail.strato.de>

[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]

Hi!

> Here are the manual backports for the upcoming 4.4 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.4.y-st-rc
>

Looks good to me.

a > 6e6dafcb73d7f x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2's op cache

I don't believe define in tools/testing/selftests/kvm/include/x86.h is
used anywhere.

a > 8e98545170c1b x86/CPU/AMD: Add X86_FEATURE_ZEN1
a > 5e0f887ad764d x86/CPU/AMD: Rename init_amd_zn() to init_amd_zen_common()
a > 6f2a036399e90 x86/CPU/AMD: Add ZenX generations flags
a > e379f10bd8fb5 ptrace: slightly saner 'get_dumpable()' logic
> 
> (All of these patches had to be manually backported to 4.19 and
again to 4.4.)

I see:

    [uli: backport to 4.19]
    Signed-off-by: Ulrich Hecht <uli@kernel.org>

I guess that should be "backport to 4.4" or perhaps even

    [uli: backport to 4.19]
    Signed-off-by: Ulrich Hecht <uli@kernel.org>
    [uli: backport to 4.4]
    Signed-off-by: Ulrich Hecht <uli@kernel.org>

But that's not a big deal.

Thanks and best regards,
								Pavel

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2026-06-09  8:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-08 15:22 Request for review for 4.4-st77, 4.4-cip112 Ulrich Hecht
2026-06-09  8:51 ` Pavel Machek [this message]
2026-06-11  1:41 ` 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=aifUAaSVDIRHHN_a@duo.ucw.cz \
    --to=pavel@nabladev.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=nobuhiro.iwamatsu.x90@mail.toshiba \
    --cc=uli@fpond.eu \
    /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