From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
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 15:07:42 +0200 [thread overview]
Message-ID: <87lhwd0vz5.fsf@intel.com> (raw)
In-Reply-To: <20140313184307.GU30571@phenom.ffwll.local>
On Thu, 13 Mar 2014, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Thu, Mar 13, 2014 at 07:52:45PM +0200, Jani Nikula wrote:
>> On Thu, 13 Mar 2014, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
>> > It's been in there since forever, and no one cared. Doesn't put a too
>> > good light onto our bug handling and QA efforts really ...
>> >
>> > References: https://bugs.freedesktop.org/attachment.cgi?id=90970
>>
>> Is there a bug report for this, or did you just spot this in an
>> unrelated bug?
>
> 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.
BR,
Jani.
> -Daniel
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-03-14 13:07 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 [this message]
2014-03-14 13:55 ` Daniel Vetter
2014-03-14 14:17 ` Jani Nikula
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=87lhwd0vz5.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--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 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.