From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Li, Yunxiang (Teddy)" <Yunxiang.Li@amd.com>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
"Koenig, Christian" <Christian.Koenig@amd.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] drm/amdgpu: fix locking scope when flushing tlb" failed to apply to 6.10-stable tree
Date: Sun, 11 Aug 2024 11:46:04 +0200 [thread overview]
Message-ID: <2024081132-sterling-serving-8b4f@gregkh> (raw)
In-Reply-To: <SA1PR12MB85999CF5386E2AADEA301076EDBA2@SA1PR12MB8599.namprd12.prod.outlook.com>
On Fri, Aug 09, 2024 at 01:37:50PM +0000, Li, Yunxiang (Teddy) wrote:
> [AMD Official Use Only - AMD Internal Distribution Only]
>
> Hi Greg,
>
> I believe this commit has already been picked onto 6.10-y as commit 84801d4f1e4fbd2c44dddecaec9099bdff100a42
Then why is it showing up here again? What broke in your workflow to
cause this? Please fix that as there are loads of these "double"
commits with no ability for me at all to detect them being a double
commit.
If this continues, I'll just end up dropping all AMD stable-marked
patches as it's too much of a hasle to deal with, and expect you all to
send me either git ids, or patch series, to apply. No other subsystem
has this issue.
greg k-h
next prev parent reply other threads:[~2024-08-11 9:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 14:16 FAILED: patch "[PATCH] drm/amdgpu: fix locking scope when flushing tlb" failed to apply to 6.10-stable tree gregkh
2024-08-09 13:37 ` Li, Yunxiang (Teddy)
2024-08-11 9:46 ` gregkh [this message]
2024-08-12 14:30 ` Li, Yunxiang (Teddy)
2024-08-12 14:43 ` gregkh
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=2024081132-sterling-serving-8b4f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Alexander.Deucher@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=Yunxiang.Li@amd.com \
--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