From: Daniel Vetter <daniel@ffwll.ch>
To: Imre Deak <imre.deak@intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 3.15-rc2] [bisected] intel framebuffer broken
Date: Tue, 22 Apr 2014 19:33:48 +0200 [thread overview]
Message-ID: <20140422173348.GX10722@phenom.ffwll.local> (raw)
In-Reply-To: <1398183760.21147.85.camel@intelbox>
On Tue, Apr 22, 2014 at 07:22:40PM +0300, Imre Deak wrote:
> On Tue, 2014-04-22 at 18:10 +0300, Jani Nikula wrote:
> > Knut, thanks for a quick bisect.
> >
> > Imre, please have a look at the sdvo WARN related to sysfs links in the
> > dmesg.
>
> It's probably the same WARN fixed by:
> http://patchwork.freedesktop.org/patch/24126/
Knut, can you please check that this patch gets rid of the WARN?
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2014-04-22 17:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 16:46 [Bug 3.15-rc2] intel framebuffer broken Knut Petersen
2014-04-22 11:54 ` Jani Nikula
2014-04-22 13:59 ` [Bug 3.15-rc2] [bisected] " Knut Petersen
2014-04-22 15:10 ` Jani Nikula
2014-04-22 16:20 ` Knut Petersen
2014-04-22 21:05 ` [PATCH] drm/i915: Discard BIOS framebuffers too small to accommodate chosen mode Chris Wilson
2014-04-23 7:11 ` Daniel Vetter
2014-04-23 7:39 ` Chris Wilson
2014-04-23 7:54 ` Chris Wilson
2014-04-23 8:24 ` Ville Syrjälä
2014-04-23 11:03 ` Jani Nikula
2014-04-23 7:50 ` Ville Syrjälä
2014-04-22 16:22 ` [Bug 3.15-rc2] [bisected] intel framebuffer broken Imre Deak
2014-04-22 17:33 ` Daniel Vetter [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=20140422173348.GX10722@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@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