All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Tim Deegan <tim@xen.org>, Ian Jackson <ian.jackson@eu.citrix.com>,
	xen-devel@lists.xen.org, Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH] domctl: revert double increment of domctl version
Date: Wed, 21 Feb 2018 19:14:50 +0100	[thread overview]
Message-ID: <20180221191450.5a693de1.olaf@aepfle.de> (raw)
In-Reply-To: <af2837e6-93dc-4552-ca3c-5e1e50c05cc0@citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 416 bytes --]

Am Wed, 21 Feb 2018 17:53:54 +0000
schrieb Andrew Cooper <andrew.cooper3@citrix.com>:

> I continue to think that this is a mistake (which is backed up by
> everyone else being confused about what is going on), and demonstrates
> the ineffectiveness of the *_INTERFACE_VERSIONS in general.

Well, my change was cosmetic anyway.
I'm updating valgrind and noticed this small inconsistency in staging.

Olaf

[-- Attachment #1.2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

      reply	other threads:[~2018-02-21 18:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21 17:34 [PATCH] domctl: revert double increment of domctl version Olaf Hering
2018-02-21 17:38 ` Wei Liu
2018-02-21 17:46   ` Olaf Hering
2018-02-21 17:53   ` Andrew Cooper
2018-02-21 18:14     ` Olaf Hering [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=20180221191450.5a693de1.olaf@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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 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.