From: Christopher James Halse Rogers <christopher.halse.rogers@canonical.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org,
Christopher James Halse Rogers <raof@ubuntu.com>
Subject: Re: [RFC PATCH 2/2] sna: Support running nested in Mir
Date: Mon, 22 Jul 2013 09:37:14 +0010 [thread overview]
Message-ID: <51ecfaff.cad4440a.2629.ffff8e7c@mx.google.com> (raw)
In-Reply-To: <20130722084143.GC16732@cantiga.alporthouse.com>
On Mon, 22 Jul, 2013 at 6:41 PM, Chris Wilson
<chris@chris-wilson.co.uk> wrote:
> On Mon, Jul 22, 2013 at 04:44:40PM +1000,
> christopher.halse.rogers@canonical.com wrote:
>> From: Christopher James Halse Rogers <raof@ubuntu.com>
>>
>> This is pretty much functional for both SNA and UXA, but can't
>> reasonably
>> be applied until the Xserver patch has landed, and that needs more
>> work.
>>
>> This demonstrates the approach, however.
>>
>> There's probably some code to be shared with XWayland support,
>> around the
>> output handling (or lack thereof) and possibly integration with the
>> underlying
>> compositor for SwapBuffers etc.
>>
> git-am doesn't like the base sha1, can you point me to a branch?
>
Oh.
Well, doesn't that make me look rather stupid. It's based on sha
2770655371, ie: 2.21.9, because that's what my master branch was up to,
and I didn't notice that it wasn't set to track origin/master. Git fail!
prev parent reply other threads:[~2013-07-22 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 6:44 [PATCH 1/2] sna: Call EnterVT from sna_screen_init christopher.halse.rogers
2013-07-22 6:44 ` [RFC PATCH 2/2] sna: Support running nested in Mir christopher.halse.rogers
2013-07-22 7:53 ` Chris Wilson
2013-07-22 8:10 ` Christopher James Halse Rogers
2013-07-22 8:33 ` Chris Wilson
2013-07-22 8:41 ` Chris Wilson
2013-07-22 9:27 ` Christopher James Halse Rogers [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=51ecfaff.cad4440a.2629.ffff8e7c@mx.google.com \
--to=christopher.halse.rogers@canonical.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=raof@ubuntu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox