From: Rusty Russell <rusty@rustcorp.com.au>
Cc: kvm@vger.kernel.org, mst@redhat.com, ericvh@gmail.com,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
v9fs-developer@lists.sourceforge.net, rminnich@sandia.gov,
Sasha Levin <sasha.levin@oracle.com>
Subject: Re: [PATCH] virtio-spec: document virtio-9p
Date: Mon, 15 Apr 2013 15:23:41 +0930 [thread overview]
Message-ID: <874nf88hlm.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1366002828-30037-1-git-send-email-sasha.levin@oracle.com>
Sasha Levin <sasha.levin@oracle.com> writes:
> Add basic documentation for virtio-9p. I can expand more on device operation,
> but I don't think there's anything significant enough for the spec to be
> mentioned there. Please let me know if I'm wrong.
>
> Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
Hmm, I guess so. I was happy to leave it undocumented.
Applied,
Rusty.
prev parent reply other threads:[~2013-04-15 5:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 5:13 [PATCH] virtio-spec: document virtio-9p Sasha Levin
2013-04-15 5:53 ` Rusty Russell [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=874nf88hlm.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=ericvh@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=rminnich@sandia.gov \
--cc=sasha.levin@oracle.com \
--cc=v9fs-developer@lists.sourceforge.net \
--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).