All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: xen-devel@lists.xensource.com, sos22@srcf.ucam.org
Subject: Re: [PATCH 1/2] PV framebuffer
Date: Mon, 13 Nov 2006 13:32:47 +0000	[thread overview]
Message-ID: <C17E247F.4692%keir@xensource.com> (raw)
In-Reply-To: <87zmavmr18.fsf@pike.pond.sub.org>




On 13/11/06 13:09, "Markus Armbruster" <armbru@redhat.com> wrote:

>> We're waiting to hear from lanana before switching to xvc. I re-submitted
>> the allocation request two weeks ago (31st October). I haven't heard
>> anything yet. I suppose since static device nodes in /dev are rare these
>> days (since everyone moved to udev) we can just squat on some device number
>> for the time being, or settle for requesting a dynamic one at boot time and
>> require use of udev for anyone who cares about the device node. We already
>> settled for that with /dev/xen/evtchn, for example.
> 
> What do you want me to do here for the short term?  Drop the patch
> hunk and let you sort it out?

It doesn't seem to have much to do with the paravirt fb patch, so probably
it should be dropped.

 -- Keir

  reply	other threads:[~2006-11-13 13:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10  8:53 [PATCH 1/2] PV framebuffer Markus Armbruster
2006-11-12 14:20 ` Steven Smith
2006-11-12 19:05   ` Keir Fraser
2006-11-13 13:09     ` Markus Armbruster
2006-11-13 13:32       ` Keir Fraser [this message]
2006-11-14 14:01   ` Markus Armbruster
2006-11-15 12:11     ` Steven Smith
2006-11-15 16:57       ` Markus Armbruster
2006-11-17  9:46         ` Steven Smith
2006-11-17 15:33     ` Markus Armbruster
2006-11-17 13:22 ` Markus Armbruster
2006-11-17 13:24   ` Markus Armbruster
2006-11-24  8:05   ` Markus Armbruster

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=C17E247F.4692%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=armbru@redhat.com \
    --cc=sos22@srcf.ucam.org \
    --cc=xen-devel@lists.xensource.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.