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: Mon, 12 Aug 2024 16:43:28 +0200 [thread overview]
Message-ID: <2024081202-rework-childcare-3069@gregkh> (raw)
In-Reply-To: <SA1PR12MB859927992245170E20E489D9ED852@SA1PR12MB8599.namprd12.prod.outlook.com>
On Mon, Aug 12, 2024 at 02:30:00PM +0000, Li, Yunxiang (Teddy) wrote:
> >From what I can piece together with git history, it seems the patch was both in amd-drm-fixes-6.10-2024-06-19 and amd-drm-next-6.11-2024-06-22 and this caused the double commit. @Deucher, Alexander
Again, PLEASE FIX YOUR BROKEN DEVELOPMENT PROCESS!
This isn't ok, and is wasting our time :(
greg k-h
prev parent reply other threads:[~2024-08-12 14:43 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
2024-08-12 14:30 ` Li, Yunxiang (Teddy)
2024-08-12 14:43 ` gregkh [this message]
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=2024081202-rework-childcare-3069@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 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.