From: Greg KH <gregkh@linuxfoundation.org>
To: Adrian Yip <adrian.ytw@gmail.com>
Cc: stable@vger.kernel.org,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
linux-kernel-mentees@lists.linux.dev, skhan@linuxfoundation.org,
david.hunter.linux@gmail.com, khalid@kernel.org
Subject: Re: [PATCH 0/4] drm/amd: Check whether secure display TA loaded successfully
Date: Mon, 20 Oct 2025 11:06:04 +0200 [thread overview]
Message-ID: <2025102014-hummus-handgun-d228@gregkh> (raw)
In-Reply-To: <20251018165653.1939869-1-adrian.ytw@gmail.com>
On Sat, Oct 18, 2025 at 11:56:40AM -0500, Adrian Yip wrote:
> Hi everyone,
>
> This is a patch series of backports from a upstream commit:
>
> c760bcda8357 ("drm/amd: Check whether secure display TA loaded successfully")
>
> to the following stable kernel trees:
> * 6.17.y
> * 6.12.y
> * 6.6.y
> * 6.1.y
>
> Each patch applied without conflicts.
>
> Compiling tests will be done for patches as I send them in.
> I have not tested backports personally, but Shuah khan has Kindly offered
> to test them.
>
> This is my first patch, please do let me know if there are any corrections
> or criticisms, I will take them to heart.
Meta-comment, do not send a "patch series" that can not all be applied
to the same tree. When applying a series of patches (1-4 as sent here),
that implies that all 4 go to the same place. That's not the case here,
so I need to pick out the patches individually some how, and apply patch
1 to one tree, 2 to another, and so on. It looks a bit odd to apply
patch 4/4 to only one tree, right?
I've picked these apart this time, but next time, just send 4 patches
separately, not as a series, as you can see others do on the stable
list, and all will be fine.
thanks,
greg k-h
next prev parent reply other threads:[~2025-10-20 9:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-18 16:56 [PATCH 0/4] drm/amd: Check whether secure display TA loaded successfully Adrian Yip
2025-10-18 16:56 ` [PATCH 1/4 6.17.y] " Adrian Yip
2025-10-18 16:56 ` [PATCH 2/4 6.12.y] " Adrian Yip
2025-10-20 9:07 ` Greg KH
2025-10-18 16:56 ` [PATCH 3/4 6.6.y] " Adrian Yip
2025-10-18 16:56 ` [PATCH 4/4 6.1.y] " Adrian Yip
2025-10-20 9:06 ` Greg KH [this message]
2025-10-20 10:22 ` [PATCH 0/4] " Adrian Yip
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=2025102014-hummus-handgun-d228@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=adrian.ytw@gmail.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=david.hunter.linux@gmail.com \
--cc=khalid@kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=simona@ffwll.ch \
--cc=skhan@linuxfoundation.org \
--cc=stable@vger.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