All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: wei.liu2@citrix.com, Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH 2/2] tools: avoid redefinining xenevtchn_handle typedef for xc_suspend_*
Date: Mon, 25 Jan 2016 18:37:54 +0100	[thread overview]
Message-ID: <20160125173754.GB14938@aepfle.de> (raw)
In-Reply-To: <1453741849-5484-2-git-send-email-ian.campbell@citrix.com>

On Mon, Jan 25, Ian Campbell wrote:

> Similar to the previous xentoollog case this is not allowed. Switch to
> a forward decl of the struct and use of it in the APIs.

Tested-by: Olaf Hering <olaf@aepfle.de>

Olaf

      parent reply	other threads:[~2016-01-25 17:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 17:10 [PATCH 2/2] tools: avoid redefinining xenevtchn_handle typedef for xc_suspend_* Ian Campbell
2016-01-25 17:22 ` Ian Jackson
2016-01-25 17:36   ` Boris Ostrovsky
2016-01-26  9:55     ` Ian Campbell
2016-01-25 17:37 ` 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=20160125173754.GB14938@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=boris.ostrovsky@oracle.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --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.