From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: David Hildenbrand <dahi@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] tools/virtio: move list macro stubs
Date: Mon, 30 Nov 2015 11:07:22 +0100 [thread overview]
Message-ID: <20151130110722.4bc1948d.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <1448872891-13717-1-git-send-email-mst@redhat.com>
On Mon, 30 Nov 2015 10:41:35 +0200
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> Makes them more generally available.
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
> tools/virtio/linux/kernel.h | 6 ++++++
> tools/virtio/linux/virtio.h | 6 ------
> 2 files changed, 6 insertions(+), 6 deletions(-)
Create a dummy list.h? Or would that be overkill?
prev parent reply other threads:[~2015-11-30 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 8:41 [PATCH] tools/virtio: move list macro stubs Michael S. Tsirkin
2015-11-30 10:07 ` Cornelia Huck [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=20151130110722.4bc1948d.cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=dahi@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.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).