From: Chris Wilson <chris@chris-wilson.co.uk>
To: Hans de Goede <hdegoede@redhat.com>
Cc: intel-gfx@lists.freedesktop.org, peter.hutterer@redhat.com
Subject: Re: [PATCH 2/2] uxa: Add support for server managed fds
Date: Tue, 18 Mar 2014 15:16:28 +0000 [thread overview]
Message-ID: <20140318151628.GP18530@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <1395152191-19258-2-git-send-email-hdegoede@redhat.com>
On Tue, Mar 18, 2014 at 03:16:31PM +0100, Hans de Goede wrote:
> I've just noticed that my previous patch-set for server managed fds misses
> out on adding server managed fds support to uxa, because uxa does its own
> /dev/dri/... device node management.
>
> This commit switches uxa over to using intel_device.c device node management.
> This is a nice cleanup and as an added bonus adds server managed fd support.
I thought this was going to be uglier... Let me double check if I was
just imagining the extra complexity.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2014-03-18 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 14:16 [PATCH 1/2] intel_device: Don't close the fd on probe failure if it is server managed Hans de Goede
2014-03-18 14:16 ` [PATCH 2/2] uxa: Add support for server managed fds Hans de Goede
2014-03-18 15:16 ` Chris Wilson [this message]
2014-03-18 16:54 ` Chris Wilson
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=20140318151628.GP18530@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=peter.hutterer@redhat.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.