stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: koos vriezen <koos.vriezen@gmail.com>
Cc: stable@vger.kernel.org, ville.syrjala@linux.intel.com
Subject: Re: FAILED: patch "[PATCH] drm/i915: tune down the fast link training vs boot fail" failed to apply to 4.9-stable tree
Date: Mon, 9 Jan 2017 13:01:31 +0100	[thread overview]
Message-ID: <20170109120131.GA13093@kroah.com> (raw)
In-Reply-To: <CAGCbPWSSe9cfWuaXS=G5eMhLF4oLE43JuJ4r7T0=Gc5LL5RofQ@mail.gmail.com>

On Mon, Jan 09, 2017 at 12:25:44PM +0100, koos vriezen wrote:
> Hi,
> 
> 2017-01-08 15:50 GMT+01:00 Greg KH <greg@kroah.com>:
> > On Sun, Jan 08, 2017 at 02:40:57PM +0100, koos vriezen wrote:
> >> Hi,
> >>
> >> Looks like "[PATCH] drm/i915: tune down the fast link training vs boot
> >> fail" is based on
> >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/i915/intel_dp.c?id=d4cb3fd9b548b8bfe2a712ec920b9ebabd3547ab
> >>
> >> Combined I get this diff
> >>
> >> --- a/drivers/gpu/drm/i915/intel_dp.c        2017-01-08 14:37:01.443536926 +0100
> >> +++ b/drivers/gpu/drm/i915/intel_dp.c      2017-01-08 14:37:17.703138505 +0100
> >> @@ -4017,6 +4017,11 @@
> >>         if (!to_intel_crtc(intel_encoder->base.crtc)->active)
> >>                 return;
> >>
> >> +       /* FIXME: we need to synchronize this sort of stuff with hardware
> >> +        * readout. Currently fast link training doesn't work on boot-up. */
> >> +       if (!intel_dp->lane_count)
> >> +               return;
> >> +
> >>         /* if link training is requested we should perform it always */
> >>         if ((intel_dp->compliance_test_type == DP_TEST_LINK_TRAINING) ||
> >>             (!drm_dp_channel_eq_ok(link_status, intel_dp->lane_count))) {
> >>
> >>
> >
> > What does that mean, I should include the previous patch as well?
> > Please be specific, I have no short-term memory :)
> 
> Just compiled with both patches and see no problem. Judging the
> d4cb3fd9b548b8bfe2a712ec920b9ebabd3547ab commit description and commit
> date, I think yes. Added Ville Syrj�l� to judge whether stable should
> have that patch.

Ok, that looks good, I've queued up both of these patches now, thanks
for the help, much appreciated.

greg k-h

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-08 13:40 FAILED: patch "[PATCH] drm/i915: tune down the fast link training vs boot fail" failed to apply to 4.9-stable tree koos vriezen
2017-01-08 14:50 ` Greg KH
2017-01-09 11:25   ` koos vriezen
2017-01-09 12:01     ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-01-06 15:48 gregkh

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=20170109120131.GA13093@kroah.com \
    --to=greg@kroah.com \
    --cc=koos.vriezen@gmail.com \
    --cc=stable@vger.kernel.org \
    --cc=ville.syrjala@linux.intel.com \
    /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).