From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
amd-gfx@lists.freedesktop.org, Xi Ruoyao <xry111@xry111.site>
Subject: Re: [PATCH v7.0.y v2 0/8] drm/amd: Backport FPU Guard Move from DML to DC
Date: Wed, 3 Jun 2026 20:05:40 -0400 [thread overview]
Message-ID: <20260603210831.item005@kernel.org> (raw)
In-Reply-To: <20260603153920.249671-1-xry111@xry111.site>
> [PATCH v7.0.y v2 0/8] drm/amd: Backport FPU Guard Move from DML to DC
> Rebased onto 7.0.11.
Thanks for the series. Unfortunately it doesn't apply to the current
7.0.y tree: patch 3/8 creates dcn42 resource files that don't exist in
this tree, and patch 5/8 depends on dml21_wrapper_fpu.c, which is not
created in 7.0.y either.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-06-04 0:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 15:39 [PATCH v7.0.y v2 0/8] drm/amd: Backport FPU Guard Move from DML to DC Xi Ruoyao
2026-06-03 15:39 ` [PATCH v7.0.y v2 1/8] drm/amd/display: Add min clock init for DML21 mode programming Xi Ruoyao
2026-06-03 15:39 ` [PATCH v7.0.y v2 2/8] drm/amd/display: Backport dml21 DC_RUN_WITH_PREEMPTION_ENABLED addition from DC 3.2.373 Xi Ruoyao
2026-06-03 15:39 ` [PATCH v7.0.y v2 3/8] drm/amd/display: Move FPU Guards From DML To DC - Part 1 Xi Ruoyao
2026-06-03 15:39 ` [PATCH v7.0.y v2 4/8] drm/amd/display: Move FPU Guards From DML To DC - Part 2 Xi Ruoyao
2026-06-03 15:39 ` [PATCH v7.0.y v2 5/8] drm/amd/display: Move FPU Guards From DML To DC - Part 3 Xi Ruoyao
2026-06-03 15:39 ` [PATCH v7.0.y v2 6/8] drm/amd/display: Fix dc_is_fp_enabled name mismatch Xi Ruoyao
2026-06-03 15:39 ` [PATCH v7.0.y v2 7/8] drm/amd/display: Fix fpu guard warning Xi Ruoyao
2026-06-03 15:39 ` [PATCH v7.0.y v2 8/8] drm/amd/display: Move dml2_destroy to non-FPU compilation unit Xi Ruoyao
2026-06-04 0:05 ` Sasha Levin [this message]
2026-06-04 3:46 ` [PATCH v7.0.y v2 0/8] drm/amd: Backport FPU Guard Move from DML to DC Xi Ruoyao
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=20260603210831.item005@kernel.org \
--to=sashal@kernel.org \
--cc=amd-gfx@lists.freedesktop.org \
--cc=stable@vger.kernel.org \
--cc=xry111@xry111.site \
/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.