All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH] xenfb shared buffer
Date: Wed, 04 Mar 2009 13:32:00 +0100	[thread overview]
Message-ID: <49AE74C0.4070909@redhat.com> (raw)
In-Reply-To: <49AE6FC6.9080307@eu.citrix.com>

Stefano Stabellini wrote:
> I am OK with these changes but I wouldn't bother removing the 16 and 32
> bpp conversion code even if currently it would never be used.
> After all is working and well tested code that may be useful in the
> future.

Well I killed it intentionally.  That way we'll notice for sure if xenfb
doesn't share the buffer although it should.  Restoring the
functionality in case we ever need it again is easy as all the magic is
in the BLT() macro anyway.

cheers
  Gerd

      reply	other threads:[~2009-03-04 12:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 18:04 [PATCH] xenfb shared buffer Stefano Stabellini
2009-03-04  7:49 ` Gerd Hoffmann
2009-03-04 12:10   ` Stefano Stabellini
2009-03-04 12:32     ` Gerd Hoffmann [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=49AE74C0.4070909@redhat.com \
    --to=kraxel@redhat.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --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.