stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Lyude Paul <lyude@redhat.com>
Cc: stable@vger.kernel.org, nouveau@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/2] drm/nouveau: Stable backport of DP clock fixes for v5.9
Date: Sat, 7 Nov 2020 16:30:27 +0100	[thread overview]
Message-ID: <20201107153027.GB90705@kroah.com> (raw)
In-Reply-To: <20201106233016.2481179-1-lyude@redhat.com>

On Fri, Nov 06, 2020 at 06:30:13PM -0500, Lyude Paul wrote:
> Just a backport of the two patches for v5.9 that you'll want to apply.
> The first one was Cc'd to stable, but I forgot to Cc the second one as
> well.
> 
> Lyude Paul (2):
>   drm/nouveau/kms/nv50-: Get rid of bogus nouveau_conn_mode_valid()
>   drm/nouveau/kms/nv50-: Fix clock checking algorithm in
>     nv50_dp_mode_valid()
> 
>  drivers/gpu/drm/nouveau/nouveau_connector.c | 36 ++++++---------------
>  drivers/gpu/drm/nouveau/nouveau_dp.c        | 21 ++++++++----
>  2 files changed, 24 insertions(+), 33 deletions(-)

Thanks for these, now queued up.

Next time if you could include what the upstream git commmit ids they
are in Linus's tree, that would help, as I have to list them.

thanks,

greg k-h

      parent reply	other threads:[~2020-11-07 15:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05 15:36 FAILED: patch "[PATCH] drm/nouveau/kms/nv50-: Get rid of bogus" failed to apply to 5.9-stable tree gregkh
2020-11-06 20:56 ` Lyude Paul
2020-11-06 23:30 ` [PATCH 0/2] drm/nouveau: Stable backport of DP clock fixes for v5.9 Lyude Paul
2020-11-06 23:30   ` [PATCH 1/2] drm/nouveau/kms/nv50-: Get rid of bogus nouveau_conn_mode_valid() Lyude Paul
2020-11-06 23:30   ` [PATCH 2/2] drm/nouveau/kms/nv50-: Fix clock checking algorithm in nv50_dp_mode_valid() Lyude Paul
2020-11-07 15:30   ` Greg KH [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=20201107153027.GB90705@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=lyude@redhat.com \
    --cc=nouveau@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).