From: Chris Wilson <chris@chris-wilson.co.uk>
To: Bryce Harrington <bryce@canonical.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 5/8] xfree86: After 2 sec, abort setting drm interface version.
Date: Mon, 18 Mar 2013 11:00:55 +0000 [thread overview]
Message-ID: <20130318110055.GA4013@cantiga.alporthouse.com> (raw)
In-Reply-To: <1363370578-30443-6-git-send-email-bryce@canonical.com>
On Fri, Mar 15, 2013 at 11:02:55AM -0700, Bryce Harrington wrote:
> And if we've had to delay booting due to not being able to set the
> interface, fess up.
I would squash this into the previous patch. Adding an infinite loop is
unpleasant, and therefore guaranteed to be hit on every bisection.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-03-18 11:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 18:02 [PATCH 0/8] Handle drm race condition Bryce Harrington
2013-03-15 18:02 ` [PATCH 1/8] xfree86: (Cleanup) Close fd if drm interface 1.4 could not be set Bryce Harrington
2013-03-15 18:02 ` [PATCH 2/8] xfree86: Track error code and add label for error handling Bryce Harrington
2013-03-15 18:02 ` [PATCH 3/8] xfree86: Provide more details on failure Bryce Harrington
2013-03-15 18:02 ` [PATCH 4/8] xfree86: Keep trying to set interface on drm until it succeeds Bryce Harrington
2013-03-15 18:02 ` [PATCH 5/8] xfree86: After 2 sec, abort setting drm interface version Bryce Harrington
2013-03-18 11:00 ` Chris Wilson [this message]
2013-03-18 20:52 ` Bryce Harrington
2013-03-15 18:02 ` [PATCH 6/8] xfree86: Fix race condition failure opening drm Bryce Harrington
2013-03-15 18:02 ` [PATCH 7/8] xfree86: Be verbose if waiting on opening the drm device Bryce Harrington
2013-03-15 18:02 ` [PATCH 8/8] xfree86: Also handle EAGAIN errors from drmSetInterfaceVersion() Bryce Harrington
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=20130318110055.GA4013@cantiga.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=bryce@canonical.com \
--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