public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Felix Kuehling <felix.kuehling@amd.com>
To: Greg KH <gregkh@linuxfoundation.org>, amd-gfx@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: AMD drm patch workflow is broken for stable trees
Date: Wed, 14 Aug 2024 16:39:29 -0400	[thread overview]
Message-ID: <07bbc66f-5689-405d-9232-87ba59d2f421@amd.com> (raw)
In-Reply-To: <2024081247-until-audacious-6383@gregkh>

On 2024-08-12 11:00, Greg KH wrote:
> Hi all,
>
> As some of you have noticed, there's a TON of failure messages being
> sent out for AMD gpu driver commits that are tagged for stable
> backports.  In short, you all are doing something really wrong with how
> you are tagging these.
Hi Greg,

I got notifications about one KFD patch failing to apply on six branches 
(6.10, 6.6, 6.1, 5.15, 5.10 and 5.4). The funny thing is, that you 
already applied this patch on two branches back in May. The emails had a 
suspicious looking date in the header (Sep 17, 2001). I wonder if there 
was some date glitch that caused a whole bunch of patches to be re-sent 
to stable somehow:

    ------------------ original commit in Linus's tree
    ------------------ From 24e82654e98e96cece5d8b919c522054456eeec6 Mon
    Sep 17 00:00:00 2001 From: Alex Deucher
    <alexander.deucher@amd.com>Date: Sun, 14 Apr 2024 13:06:39 -0400
    Subject: [PATCH] drm/amdkfd: don't allow mapping the MMIO HDP page
    with large pages ...

On 6.1 and 6.6, the patch was already applied by you in May:

    $ git log --pretty=fuller stable/linux-6.6.y --grep "drm/amdkfd: don't allow mapping the MMIO HDP page with large pages"
    commit 4b4cff994a27ebf7bd3fb9a798a1cdfa8d01b724
    Author:     Alex Deucher <alexander.deucher@amd.com>
    AuthorDate: Sun Apr 14 13:06:39 2024 -0400
    Commit:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    CommitDate: Fri May 17 12:02:34 2024 +0200

         drm/amdkfd: don't allow mapping the MMIO HDP page with large pages
    ...

On 6.10 it was already upstream.

On 5.4-5.15 it doesn't apply because of conflicts. I can resolve those 
and send the fixed patches out for you.

Regards,
   Felix


>
> Please fix it up to NOT have duplicates in multiple branches that end up
> in Linus's tree at different times.  Or if you MUST do that, then give
> us a chance to figure out that it IS a duplicate.  As-is, it's not
> working at all, and I think I need to just drop all patches for this
> driver that are tagged for stable going forward and rely on you all to
> provide a proper set of backported fixes when you say they are needed.
>
> Again, what you are doing today is NOT ok and is broken.  Please fix.
>
> greg k-h

  reply	other threads:[~2024-08-14 20:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-12 15:00 AMD drm patch workflow is broken for stable trees Greg KH
2024-08-14 20:39 ` Felix Kuehling [this message]
2024-08-14 21:30   ` Alex Deucher
2024-08-15  5:11     ` Greg KH
2024-08-23 21:23       ` Alex Deucher
2024-08-24  5:23         ` Greg KH
2024-08-27 14:18           ` Alex Deucher
2024-09-04 17:23             ` Greg KH
2024-09-30 14:10               ` Alex Deucher
2024-10-01 10:04                 ` Greg KH
2024-10-01 13:19                   ` Alex Deucher
2024-08-15  5:12   ` Greg KH

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=07bbc66f-5689-405d-9232-87ba59d2f421@amd.com \
    --to=felix.kuehling@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=gregkh@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