All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <mdaenzer@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: alexander.deucher@amd.com, lyude@redhat.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] drm/amdgpu: Drop inline from" failed to apply to 5.14-stable tree
Date: Mon, 20 Sep 2021 11:11:51 +0200	[thread overview]
Message-ID: <b925253e-5893-5e13-967b-1ab2121f9c15@redhat.com> (raw)
In-Reply-To: <YUhOXI4VFfpvheQo@kroah.com>

On 2021-09-20 11:03, Greg KH wrote:
> On Mon, Sep 20, 2021 at 10:57:34AM +0200, Michel Dänzer wrote:
>> On 2021-09-20 10:52, gregkh@linuxfoundation.org wrote:
>>>
>>> The patch below does not apply to the 5.14-stable tree.
>>> If someone wants it applied there, or to any other stable or longterm
>>> tree, then please email the backport, including the original git commit
>>> id to <stable@vger.kernel.org>.
>>
>> I wrote a comment above the Fixes line:
>>
>> # The function is called amdgpu_ras_eeprom_get_record_max_length on
>> # stable branches
>>
>>
>> Looks like that got lost somewhere along the way.
> 
> Can you send a working patch for these older kernels that I can queue
> up?

Actually, it's not critical to have this on the stable branches, let's 
just drop it.


-- 
Earthling Michel Dänzer               |               https://redhat.com
Libre software enthusiast             |             Mesa and X developer


  reply	other threads:[~2021-09-20  9:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-20  8:52 FAILED: patch "[PATCH] drm/amdgpu: Drop inline from" failed to apply to 5.14-stable tree gregkh
     [not found] ` <d35b1d9f-6cbf-d0d6-bb0e-0e15919eced5@redhat.com>
2021-09-20  9:03   ` Greg KH
2021-09-20  9:11     ` Michel Dänzer [this message]
2021-09-20  9:19       ` 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=b925253e-5893-5e13-967b-1ab2121f9c15@redhat.com \
    --to=mdaenzer@redhat.com \
    --cc=alexander.deucher@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=lyude@redhat.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.