From: Cornelia Huck <cohuck@redhat.com>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
Cc: virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, stefanha@redhat.com
Subject: [virtio-comment] Re: [PATCH v2 2/3] shared memory: Define PCI capability
Date: Fri, 22 Feb 2019 13:50:03 +0100 [thread overview]
Message-ID: <20190222135003.307b797e.cohuck@redhat.com> (raw)
In-Reply-To: <20190222115433.7160-3-dgilbert@redhat.com>
On Fri, 22 Feb 2019 11:54:32 +0000
"Dr. David Alan Gilbert (git)" <dgilbert@redhat.com> wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>
> Define the PCI capability used for enumerating shared memory regions.
>
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> content.tex | 37 +++++++++++++++++++++++++++++++++++++
> 1 file changed, 37 insertions(+)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2019-02-22 12:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 11:54 [virtio-comment] [PATCH v2 0/3] Large shared memory regions Dr. David Alan Gilbert (git)
2019-02-22 11:54 ` [virtio-comment] [PATCH v2 1/3] shared memory: Define " Dr. David Alan Gilbert (git)
2019-02-22 12:48 ` [virtio-comment] " Cornelia Huck
2019-02-25 16:37 ` Stefan Hajnoczi
2019-02-26 15:11 ` [virtio-comment] Re: [virtio-dev] " Dr. David Alan Gilbert
2019-02-26 15:40 ` Halil Pasic
2019-02-26 15:43 ` Cornelia Huck
2019-03-04 12:46 ` Dr. David Alan Gilbert
2019-02-22 11:54 ` [virtio-comment] [PATCH v2 2/3] shared memory: Define PCI capability Dr. David Alan Gilbert (git)
2019-02-22 12:50 ` Cornelia Huck [this message]
2019-02-22 11:54 ` [virtio-comment] [PATCH v2 3/3] shared memory: Define mmio registers Dr. David Alan Gilbert (git)
2019-02-25 16:50 ` [virtio-comment] " Stefan Hajnoczi
2019-02-25 18:45 ` Dr. David Alan Gilbert
2019-02-27 13:56 ` Cornelia Huck
2019-02-27 17:06 ` Stefan Hajnoczi
2019-02-27 18:37 ` [virtio-comment] Re: [virtio-dev] " Dr. David Alan Gilbert
2019-02-27 18:52 ` Dr. David Alan Gilbert
2019-02-27 13:50 ` Cornelia Huck
2019-02-27 18:33 ` [virtio-comment] Re: [virtio-dev] " Dr. David Alan Gilbert
2019-03-05 15:47 ` [virtio-comment] [PATCH v2 0/3] Large shared memory regions Frank Yang
2019-06-17 18:38 ` Michael S. Tsirkin
2019-06-17 18:59 ` Frank Yang
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=20190222135003.307b797e.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=dgilbert@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.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