From: Christoph Hellwig <hch@infradead.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] virtio_mmio: expose header to userspace
Date: Thu, 12 Jan 2017 23:58:22 -0800 [thread overview]
Message-ID: <20170113075822.GA31777@infradead.org> (raw)
In-Reply-To: <1484257033-11032-1-git-send-email-mst@redhat.com>
On Thu, Jan 12, 2017 at 11:37:22PM +0200, Michael S. Tsirkin wrote:
> It's handy for userspace emulators like QEMU.
But it's not actually a userspace API - it's an on the write protocol.
so: NAK.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: linux-kernel@vger.kernel.org, Jason Wang <jasowang@redhat.com>,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] virtio_mmio: expose header to userspace
Date: Thu, 12 Jan 2017 23:58:22 -0800 [thread overview]
Message-ID: <20170113075822.GA31777@infradead.org> (raw)
In-Reply-To: <1484257033-11032-1-git-send-email-mst@redhat.com>
On Thu, Jan 12, 2017 at 11:37:22PM +0200, Michael S. Tsirkin wrote:
> It's handy for userspace emulators like QEMU.
But it's not actually a userspace API - it's an on the write protocol.
so: NAK.
next prev parent reply other threads:[~2017-01-13 7:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 21:37 [PATCH] virtio_mmio: expose header to userspace Michael S. Tsirkin
2017-01-13 3:10 ` Jason Wang
2017-01-13 3:10 ` Jason Wang
2017-01-13 7:58 ` Christoph Hellwig [this message]
2017-01-13 7:58 ` Christoph Hellwig
2017-01-13 13:31 ` Michael S. Tsirkin
2017-01-13 13:31 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2017-01-12 21:37 Michael S. Tsirkin
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=20170113075822.GA31777@infradead.org \
--to=hch@infradead.org \
--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 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.