From: Jason Wang <jasowang@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>,
Randy Dunlap <rdunlap@infradead.org>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org,
intel-gvt-dev@lists.freedesktop.org, kwankhede@nvidia.com,
mst@redhat.com, tiwei.bie@intel.com,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, cohuck@redhat.com,
maxime.coquelin@redhat.com, cunming.liang@intel.com,
zhihong.wang@intel.com, rob.miller@broadcom.com,
xiao.w.wang@intel.com, haotian.wang@sifive.com,
zhenyuw@linux.intel.com, zhi.a.wang@intel.com,
jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
rodrigo.vivi@intel.com, airlied@linux.ie, daniel@ffwll.ch,
farman@linux.ibm.com, pasic@linux.ibm.com, sebott@linux.ibm.com,
oberpar@linux.ibm.com, heiko.carstens@de.ibm.com,
gor@linux.ibm.com, borntraeger@de.ibm.com,
akrowiak@linux.ibm.com, freude@linux.ibm.com,
lingshan.zhu@intel.com, idos@mellanox.com, eperezma@redhat.com,
lulu@redhat.com, parav@mellanox.com,
christophe.de.dinechin@gmail.com, kevin.tian@intel.com,
stefanha@redhat.com
Subject: Re: [PATCH V9 6/6] docs: sample driver to demonstrate how to implement virtio-mdev framework
Date: Thu, 7 Nov 2019 22:30:37 +0800 [thread overview]
Message-ID: <1b26d298-0223-c5cc-9dd6-c4005139e32a@redhat.com> (raw)
In-Reply-To: <20191106155800.0b8418ec@x1.home>
On 2019/11/7 上午6:58, Alex Williamson wrote:
> On Wed, 6 Nov 2019 14:50:30 -0800
> Randy Dunlap <rdunlap@infradead.org> wrote:
>
>> On 11/5/19 11:05 PM, Jason Wang wrote:
>>> diff --git a/samples/Kconfig b/samples/Kconfig
>>> index c8dacb4dda80..13a2443e18e0 100644
>>> --- a/samples/Kconfig
>>> +++ b/samples/Kconfig
>>> @@ -131,6 +131,16 @@ config SAMPLE_VFIO_MDEV_MDPY
>>> mediated device. It is a simple framebuffer and supports
>>> the region display interface (VFIO_GFX_PLANE_TYPE_REGION).
>>>
>>> +config SAMPLE_VIRTIO_MDEV_NET
>>> + tristate "Build VIRTIO net example mediated device sample code -- loadable modules only"
>>> + depends on VIRTIO_MDEV && VHOST_RING && m
>>> + help
>>> + Build a networking sample device for use as a virtio
>>> + mediated device. The device coopreates with virtio-mdev bus
>> typo here:
>> cooperates
>>
> I can fix this on commit relative to V10 if there are no other issues
> raised:
>
> diff --git a/samples/Kconfig b/samples/Kconfig
> index 13a2443e18e0..b7116d97cbbe 100644
> --- a/samples/Kconfig
> +++ b/samples/Kconfig
> @@ -136,7 +136,7 @@ config SAMPLE_VIRTIO_MDEV_NET
> depends on VIRTIO_MDEV && VHOST_RING && m
> help
> Build a networking sample device for use as a virtio
> - mediated device. The device coopreates with virtio-mdev bus
> + mediated device. The device cooperates with virtio-mdev bus
> driver to present an virtio ethernet driver for
> kernel. It simply loopbacks all packets from its TX
> virtqueue to its RX virtqueue.
>
> Thanks,
> Alex
Thanks, per Michael request, I would rename mvnet and include this fix
in V11.
>
next prev parent reply other threads:[~2019-11-07 14:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 7:05 [PATCH V9 0/6] mdev based hardware virtio offloading support Jason Wang
2019-11-06 7:05 ` [PATCH V9 1/6] mdev: class id support Jason Wang
2019-11-06 7:05 ` [PATCH V9 2/6] modpost: add support for mdev class id Jason Wang
2019-11-06 7:05 ` [PATCH V9 3/6] mdev: introduce device specific ops Jason Wang
2019-11-06 10:52 ` Cornelia Huck
2019-11-06 7:05 ` [PATCH V9 4/6] mdev: introduce virtio device and its device ops Jason Wang
2019-11-06 10:53 ` Cornelia Huck
2019-11-06 7:05 ` [PATCH V9 5/6] virtio: introduce a mdev based transport Jason Wang
2019-11-06 11:00 ` Cornelia Huck
2019-11-06 13:11 ` Jason Wang
2019-11-06 7:05 ` [PATCH V9 6/6] docs: sample driver to demonstrate how to implement virtio-mdev framework Jason Wang
2019-11-06 22:50 ` Randy Dunlap
2019-11-06 22:58 ` Alex Williamson
2019-11-07 14:30 ` Jason Wang [this message]
2019-11-07 9:01 ` [PATCH V9 0/6] mdev based hardware virtio offloading support 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=1b26d298-0223-c5cc-9dd6-c4005139e32a@redhat.com \
--to=jasowang@redhat.com \
--cc=airlied@linux.ie \
--cc=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=christophe.de.dinechin@gmail.com \
--cc=cohuck@redhat.com \
--cc=cunming.liang@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=eperezma@redhat.com \
--cc=farman@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=haotian.wang@sifive.com \
--cc=heiko.carstens@de.ibm.com \
--cc=idos@mellanox.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=lingshan.zhu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=oberpar@linux.ibm.com \
--cc=parav@mellanox.com \
--cc=pasic@linux.ibm.com \
--cc=rdunlap@infradead.org \
--cc=rob.miller@broadcom.com \
--cc=rodrigo.vivi@intel.com \
--cc=sebott@linux.ibm.com \
--cc=stefanha@redhat.com \
--cc=tiwei.bie@intel.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xiao.w.wang@intel.com \
--cc=zhenyuw@linux.intel.com \
--cc=zhi.a.wang@intel.com \
--cc=zhihong.wang@intel.com \
/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
all inboxes | Powered by JetHome®