From: Dave Young <dyoung@redhat.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: daniel.vetter@intel.com, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH]i915: use WARN_ON_ONCE in intel_dp_aux_transfer
Date: Thu, 1 Dec 2016 16:02:50 +0800 [thread overview]
Message-ID: <20161201080250.GA14723@dhcp-128-65.nay.redhat.com> (raw)
In-Reply-To: <20161201080002.GA14682@dhcp-128-65.nay.redhat.com>
On 12/01/16 at 04:00pm, Dave Young wrote:
> On 11/30/16 at 03:25pm, Ville Syrjälä wrote:
> > On Thu, Nov 24, 2016 at 05:03:20PM +0800, Dave Young wrote:
> > > On 11/24/16 at 10:53am, Jani Nikula wrote:
> > > > On Thu, 24 Nov 2016, Dave Young <dyoung@redhat.com> wrote:
> > > > > I see a lot of below warning:
> > > >
> > > > No, we must not hide this under the carpet. There's a bug at fdo about
> > > > this, and we need to fix it.
> > >
> > > It is not hiding it, just not repeating the warnings. But anyway I do
> > > not have strong opinion. I'm building my kernel with this patch until
> > > there is a real fix in upstream.
> >
> > We already have a patch to reduce it a single WARN:
> > d4cb3fd9b548 ("drm/i915/dp: add lane_count check in intel_dp_check_link_status")
>
> It works for me, thanks
>
> >
> > Do we need to get that backported to stable?
>
> Personally I think it should but I'm not sure the policy of stable for i915 though.
>
Hmm, I can not recall when I had such issue in which version of kernel
because I just pull and rebuild very often, so I should say I have no
idea ..
> Thanks
> Dave
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-12-01 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 8:11 [PATCH]i915: use WARN_ON_ONCE in intel_dp_aux_transfer Dave Young
2016-11-24 8:53 ` Jani Nikula
2016-11-24 9:03 ` Dave Young
2016-11-30 13:25 ` Ville Syrjälä
2016-12-01 8:00 ` Dave Young
2016-12-01 8:02 ` Dave Young [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=20161201080250.GA14723@dhcp-128-65.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.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).