qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alon Levy <alevy@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 1/2] qxl: add QXL_IO_MONITORS_CONFIG_ASYNC
Date: Wed, 15 Aug 2012 13:32:27 +0300	[thread overview]
Message-ID: <20120815103227.GH17706@garlic.redhat.com> (raw)
In-Reply-To: <502B5C7B.4020502@redhat.com>

On Wed, Aug 15, 2012 at 10:23:23AM +0200, Gerd Hoffmann wrote:
> On 08/09/12 16:21, Alon Levy wrote:
> > Revision bumped to 4 for new IO support, enabled for spice-server >=
> > 0.11.1. New io enabled iff spice-server >= 0.11.1 && spice-protocol >=
> > 0.12.0.
> 
> Patch doesn't apply cleanly to master.

Strange, will resend.

> 
> > +    if $pkg_config --atleast-version=0.12.0 spice-protocol >/dev/null 2>&1; then
> > +        QEMU_CFLAGS="$QEMU_CFLAGS -DQXL_HAS_IO_MONITORS_CONFIG_ASYNC"
> > +    fi
> 
> /me thinks now with spice-server having no dependency any more on
> spice-protocol we should add a #define SPICE_PROTOCOL_VERSION to
> spice-protocol so we don't need constructs like this.

So yet another place to remember to update the version number. But I
agree it's cleaner.

> 
> Or maybe just use
> 
> #ifndef QXL_HAS_IO_MONITORS_CONFIG_ASYNC
> #define QXL_HAS_IO_MONITORS_CONFIG_ASYNC $whatever
> #endif

I don't get this. You mean to have add
#define QXL_HAS_IO_MONITORS_CONFIG_ASYNC bla
to spice-protocol?

> 
> ?
> 
> > +#if SPICE_SERVER_VERSION >= 0x000b01 /* 0.11.1 */
> > +#ifdef QXL_HAS_IO_MONITORS_CONFIG_ASYNC
> 
> Can be on a single line:
> 
> #if (SPICE_SERVER_VERSION >= 0x000b01) &&
> defined(QXL_HAS_IO_MONITORS_CONFIG_ASYNC)
> 
> Or:
> 
> #if (SPICE_SERVER_VERSION >= 0x000b01) && (SPICE_PROTOCOL_VERSION >= ...)
> 

Correct, the point was to make sure when I later removed only a part of
it it would show up as a single line removal. But sure, if you prefer it
this way.

> cheers,
>   Gerd
> 

  reply	other threads:[~2012-08-15 10:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23 13:08 [Qemu-devel] [PATCH 1/2] qxl: disallow unknown revisions Alon Levy
2012-07-23 13:08 ` [Qemu-devel] [PATCH 2/2] qxl: add QXL_IO_MONITORS_CONFIG_ASYNC Alon Levy
2012-07-23 16:33   ` [Qemu-devel] [PATCH v2] " Alon Levy
2012-07-25  9:00     ` Yonit Halperin
2012-07-25 17:29       ` Alon Levy
2012-07-26  5:26         ` Yonit Halperin
2012-07-28  8:56         ` Alon Levy
2012-07-28  9:01           ` Blue Swirl
2012-07-28 10:20             ` Alon Levy
2012-07-28 10:23             ` [Qemu-devel] [PATCH v3] " Alon Levy
2012-08-06  7:31               ` Gerd Hoffmann
2012-08-09 13:41                 ` Alon Levy
2012-08-09 13:50                   ` Gerd Hoffmann
2012-08-09 14:18                     ` Alon Levy
2012-08-09 14:21                     ` [Qemu-devel] [PATCH v4 1/2] " Alon Levy
2012-08-09 14:21                       ` [Qemu-devel] [PATCH v4 2/2] configure: print spice-protocol and spice-server versions Alon Levy
2012-08-15  8:23                       ` [Qemu-devel] [PATCH v4 1/2] qxl: add QXL_IO_MONITORS_CONFIG_ASYNC Gerd Hoffmann
2012-08-15 10:32                         ` Alon Levy [this message]
2012-08-15 10:43                           ` Gerd Hoffmann

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=20120815103227.GH17706@garlic.redhat.com \
    --to=alevy@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).