From: Alan Stern <stern@rowland.harvard.edu>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
"Kernel development list" <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] Excessive WARN()s in Intel 915 driver
Date: Thu, 30 Jan 2014 10:52:04 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44L0.1401301051000.1833-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <20140130152258.GS17001@phenom.ffwll.local>
On Thu, 30 Jan 2014, Daniel Vetter wrote:
> Ok, I seem to have been truly blind all the time. This seems to have been
> fallout from
>
> commit b6c5164d7bf624f3e1b750787ddb983150c5117c
> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> Date: Fri Apr 12 18:48:43 2013 +0200
>
> drm/i915: Fixup Oops in the pipe config computation
>
> Meanwhile we've moved the overall infrastructure ahead again quite a bit,
> so I think it's time to give the full atomic modeset paths another shot.
> But I'll be travelling to fosdem the next few days, so this will take a
> bit of time.
>
> As long as there's not real bad side-effects I guess we simply need to
> live with the WARN for a tad longer.
Okay. Let me know when you've got something else ready to test.
Alan Stern
WARNING: multiple messages have this Message-ID (diff)
From: Alan Stern <stern@rowland.harvard.edu>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: Excessive WARN()s in Intel 915 driver
Date: Thu, 30 Jan 2014 10:52:04 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44L0.1401301051000.1833-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <20140130152258.GS17001@phenom.ffwll.local>
On Thu, 30 Jan 2014, Daniel Vetter wrote:
> Ok, I seem to have been truly blind all the time. This seems to have been
> fallout from
>
> commit b6c5164d7bf624f3e1b750787ddb983150c5117c
> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> Date: Fri Apr 12 18:48:43 2013 +0200
>
> drm/i915: Fixup Oops in the pipe config computation
>
> Meanwhile we've moved the overall infrastructure ahead again quite a bit,
> so I think it's time to give the full atomic modeset paths another shot.
> But I'll be travelling to fosdem the next few days, so this will take a
> bit of time.
>
> As long as there's not real bad side-effects I guess we simply need to
> live with the WARN for a tad longer.
Okay. Let me know when you've got something else ready to test.
Alan Stern
next prev parent reply other threads:[~2014-01-30 15:52 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 18:50 Excessive WARN()s in Intel 915 driver Alan Stern
2014-01-07 20:12 ` Daniel Vetter
2014-01-08 16:08 ` Alan Stern
2014-01-08 16:17 ` Daniel Vetter
2014-01-08 18:34 ` Alan Stern
2014-01-08 20:21 ` Daniel Vetter
2014-01-08 20:21 ` Daniel Vetter
2014-01-08 23:15 ` Alan Stern
2014-01-13 20:16 ` Alan Stern
2014-01-14 9:05 ` Daniel Vetter
2014-01-14 14:43 ` Alan Stern
2014-01-27 9:02 ` Daniel Vetter
2014-01-27 15:30 ` Alan Stern
2014-01-27 15:56 ` Daniel Vetter
2014-01-27 16:05 ` Alan Stern
2014-01-27 16:36 ` Daniel Vetter
2014-01-27 16:36 ` Daniel Vetter
2014-01-27 17:14 ` Alan Stern
2014-01-28 16:34 ` Alan Stern
2014-01-28 16:34 ` Alan Stern
2014-01-14 12:52 ` [Intel-gfx] " Jani Nikula
2014-01-08 18:43 ` Ville Syrjälä
2014-01-08 18:43 ` Ville Syrjälä
2014-01-28 17:17 ` [Intel-gfx] " Daniel Vetter
2014-01-28 17:17 ` Daniel Vetter
2014-01-28 19:42 ` [Intel-gfx] " Daniel Vetter
2014-01-28 19:42 ` Daniel Vetter
2014-01-30 14:53 ` [Intel-gfx] " Alan Stern
2014-01-30 14:53 ` Alan Stern
2014-01-30 15:22 ` [Intel-gfx] " Daniel Vetter
2014-01-30 15:22 ` Daniel Vetter
2014-01-30 15:52 ` Alan Stern [this message]
2014-01-30 15:52 ` Alan Stern
2014-06-25 18:06 ` Regression in i915 driver in 3.16-rc2 Alan Stern
2014-06-25 18:26 ` [Intel-gfx] " Ville Syrjälä
2014-06-25 18:26 ` Ville Syrjälä
2014-06-25 18:50 ` [Intel-gfx] " Alan Stern
2014-06-25 18:50 ` Alan Stern
2014-06-30 10:52 ` [Intel-gfx] " Jani Nikula
2014-06-30 10:52 ` 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=Pine.LNX.4.44L0.1401301051000.1833-100000@iolanthe.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@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 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.