From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Remove erronous WARN in the vlv pipe crc code
Date: Fri, 14 Mar 2014 16:17:06 +0200 [thread overview]
Message-ID: <87fvmk27bx.fsf@intel.com> (raw)
In-Reply-To: <CAKMK7uHKys=qOvmd4H40aBSTz9-b6XPh-o1xG_++nnn=yESE_g@mail.gmail.com>
On Fri, 14 Mar 2014, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Fri, Mar 14, 2014 at 2:07 PM, Jani Nikula
> <jani.nikula@linux.intel.com> wrote:
>>> The bug report complains that the crc stuff doesn't work on byt edp, but
>>> dmesg contains a pile of these WARNs. Hence just references, since this
>>> likely won't fix the actual bug.
>>
>> Pushed to -fixes, thanks for the patch.
>
> Imo not -fixes material, since only our own validation tools can hit
> this. And only through debugfs, so not even nasty userspace can
> trigger this without being root.
Pulled back from -fixes. It didn't happen.
Jani.
--
Jani Nikula, Intel Open Source Technology Center
prev parent reply other threads:[~2014-03-14 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 16:46 [PATCH] drm/i915: Remove erronous WARN in the vlv pipe crc code Daniel Vetter
2014-03-13 17:52 ` Jani Nikula
2014-03-13 18:43 ` Daniel Vetter
2014-03-14 13:07 ` Jani Nikula
2014-03-14 13:55 ` Daniel Vetter
2014-03-14 14:17 ` Jani Nikula [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=87fvmk27bx.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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