All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: <gregkh@linuxfoundation.org>
Cc: Flora.Cui@amd.com, Qingqing.Wang@amd.com,
	alexander.deucher@amd.com, christian.koenig@amd.com,
	maraeo@gmail.com, marek.olsak@amd.com, <stable@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] drm/amdgpu: Fix undue fallthroughs in golden registers" failed to apply to 4.13-stable tree
Date: Wed, 20 Sep 2017 14:57:46 +0200	[thread overview]
Message-ID: <20170920145746.7df2002b@endymion> (raw)
In-Reply-To: <1505898989160217@kroah.com>

Hi Greg,

On Wed, 20 Sep 2017 11:16:29 +0200, gregkh@linuxfoundation.org wrote:
> The patch below does not apply to the 4.13-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>.
> 
> thanks,
> 
> greg k-h
> 
> ------------------ original commit in Linus's tree ------------------
> 
> From 2db93bea4bba79d35ac4576d4acef2101a62288d Mon Sep 17 00:00:00 2001
> From: Jean Delvare <jdelvare@suse.de>
> Date: Sun, 30 Jul 2017 10:18:25 +0200
> Subject: [PATCH] drm/amdgpu: Fix undue fallthroughs in golden registers
>  initialization

This fix was already in 4.13 (and is also in 4.9-stable for that
matter.) Somehow this fix appears twice in the git log, once as
5694785cf09b and once as 2db93bea4bba. No idea how this is possible.

Anyway, all is fine here, nothing to backport.

-- 
Jean Delvare
SUSE L3 Support

      reply	other threads:[~2017-09-20 12:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20  9:16 FAILED: patch "[PATCH] drm/amdgpu: Fix undue fallthroughs in golden registers" failed to apply to 4.13-stable tree gregkh
2017-09-20 12:57 ` Jean Delvare [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=20170920145746.7df2002b@endymion \
    --to=jdelvare@suse.de \
    --cc=Flora.Cui@amd.com \
    --cc=Qingqing.Wang@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=maraeo@gmail.com \
    --cc=marek.olsak@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.