DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Bruce Richardson" <bruce.richardson@intel.com>, <dev@dpdk.org>
Cc: "Maxime Coquelin" <maxime.coquelin@redhat.com>,
	"Chenbo Xia" <chenbo.xia@intel.com>
Subject: RE: [PATCH v3 0/4] Enhance docs on virtio-user as KNI replacement
Date: Fri, 10 Jun 2022 17:58:24 +0200	[thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D87112@smartserver.smartshare.dk> (raw)
In-Reply-To: <20220610153535.659076-1-bruce.richardson@intel.com>

> From: Bruce Richardson [mailto:bruce.richardson@intel.com]
> Sent: Friday, 10 June 2022 17.36
> 
> Since use of KNI is no longer advised (due to known issues and the fact
> it's an out-of-tree module), virtio-user is recommended for new
> developments. To help encourage this, we improve the doc HOWTO section
> on using virtio-user and add a link to that document from the main KNI
> section in the programmers guide.
> 
> v3:
> * Added two extra patches:
>   - rename document files to match new section name
>   - add note to KNI programmers guide section
> * minor updates to patch 2, and added stable on CC for that patch
> 
> Bruce Richardson (4):
>   doc/howto: rework section on virtio-user as exception path
>   doc/howto: rename files to match new content name
>   doc/howto: add code example to virtio-user exception path doc
>   doc/prog_guide: add reference to virtio-user from KNI doc
> 
>  ....svg => virtio_user_as_exception_path.svg} |   0
>  doc/guides/howto/index.rst                    |   2 +-
>  .../howto/virtio_user_as_exception_path.rst   | 214 ++++++++++++++++++
>  .../howto/virtio_user_as_exceptional_path.rst | 118 ----------
>  .../prog_guide/kernel_nic_interface.rst       |   6 +
>  5 files changed, 221 insertions(+), 119 deletions(-)
>  rename doc/guides/howto/img/{virtio_user_as_exceptional_path.svg =>
> virtio_user_as_exception_path.svg} (100%)
>  create mode 100644 doc/guides/howto/virtio_user_as_exception_path.rst
>  delete mode 100644
> doc/guides/howto/virtio_user_as_exceptional_path.rst
> 
> --
> 2.34.1
> 

Yes.

Series-Acked-by: Morten Brørup <mb@smartsharesystems.com>


  parent reply	other threads:[~2022-06-10 15:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 16:26 [PATCH 1/2] doc/howto: rework section on virtio-user as exception path Bruce Richardson
2022-05-27 16:26 ` [PATCH 2/2] doc/howto: add code example to virtio-user exception path doc Bruce Richardson
2022-05-27 16:36 ` [PATCH v2 1/2] doc/howto: rework section on virtio-user as exception path Bruce Richardson
2022-05-27 16:36   ` [PATCH v2 2/2] doc/howto: add code example to virtio-user exception path doc Bruce Richardson
2022-05-27 18:03     ` Stephen Hemminger
2022-05-30  5:44     ` Xia, Chenbo
2022-06-10 14:33       ` Bruce Richardson
2022-05-30  5:33   ` [PATCH v2 1/2] doc/howto: rework section on virtio-user as exception path Xia, Chenbo
2022-06-10 14:36     ` Bruce Richardson
2022-06-10 15:35 ` [PATCH v3 0/4] Enhance docs on virtio-user as KNI replacement Bruce Richardson
2022-06-10 15:35   ` [PATCH v3 1/4] doc/howto: rework section on virtio-user as exception path Bruce Richardson
2022-06-15  1:44     ` Xia, Chenbo
2022-07-01 12:59     ` Maxime Coquelin
2022-07-11 13:10     ` Thomas Monjalon
2022-07-11 13:18       ` Bruce Richardson
2022-06-10 15:35   ` [PATCH v3 2/4] doc/howto: rename files to match new content name Bruce Richardson
2022-06-15  1:45     ` Xia, Chenbo
2022-07-07 15:38     ` Maxime Coquelin
2022-06-10 15:35   ` [PATCH v3 3/4] doc/howto: add code example to virtio-user exception path doc Bruce Richardson
2022-06-15  1:47     ` Xia, Chenbo
2022-07-07 15:50     ` Maxime Coquelin
2022-06-10 15:35   ` [PATCH v3 4/4] doc/prog_guide: add reference to virtio-user from KNI doc Bruce Richardson
2022-06-15  1:47     ` Xia, Chenbo
2022-07-07 15:52     ` Maxime Coquelin
2022-06-10 15:58   ` Morten Brørup [this message]
2022-07-08  9:12   ` [PATCH v3 0/4] Enhance docs on virtio-user as KNI replacement Maxime Coquelin

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=98CBD80474FA8B44BF855DF32C47DC35D87112@smartserver.smartshare.dk \
    --to=mb@smartsharesystems.com \
    --cc=bruce.richardson@intel.com \
    --cc=chenbo.xia@intel.com \
    --cc=dev@dpdk.org \
    --cc=maxime.coquelin@redhat.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;
as well as URLs for NNTP newsgroup(s).