From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>,
maxime.coquelin@redhat.com
Cc: dev@dpdk.org, david.marchand@redhat.com, ferruh.yigit@intel.com,
jerinj@marvell.com
Subject: Re: [dpdk-dev] [PATCH v2] kernel: remove igb_uio
Date: Mon, 05 Oct 2020 10:57:54 +0200 [thread overview]
Message-ID: <9651014.gTjpZimMdh@thomas> (raw)
In-Reply-To: <20200923224124.494c2e9a@hermes.lan>
24/09/2020 07:41, Stephen Hemminger:
> On Fri, 11 Sep 2020 17:54:48 +0200
> Thomas Monjalon <thomas@monjalon.net> wrote:
>
> > As decided in the Technical Board in November 2019,
> > the kernel module igb_uio is moved to the dpdk-kmods repository
> > in the /linux/igb_uio/ directory.
> >
> > Minutes of Technical Board meeting:
> > https://mails.dpdk.org/archives/dev/2019-November/151763.html
> >
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> > ---
> > v2: update few docs (including release notes)
>
> Good so far:
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
>
> You may want to address all the references to igb_uio in guides/nics
>
> ark.rst
> axgbe.rst
> bnx2x.rst
> bnxt.rst
> build_and_test.rst
> ena.rst
> enic.rst
> features.rst
> hns3.rst
> i40e.rst
> intel_vf.rst
> ixgbe.rst
> liquidio.rst
> mlx4.rst
> mlx5.rst
> nfp.rst
> qede.rst
> virtio.rst
igb_uio is still available.
A next step in deprecation might be to remove igb_uio references.
> What about drivers like ark which don't mention vfio?
They should be updated by their maintainer.
> Does virtio still require igb_uio? or x86 I/O port for doorbell?
> Or is this just stale language.
Maxime, any update on the use of igb_uio with virtio?
next prev parent reply other threads:[~2020-10-05 8:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 22:50 [dpdk-dev] [PATCH] " Thomas Monjalon
2020-09-08 0:14 ` Thomas Monjalon
2020-09-08 8:25 ` Bruce Richardson
2020-09-08 9:27 ` Thomas Monjalon
2020-09-08 9:34 ` Bruce Richardson
2020-09-08 9:46 ` Thomas Monjalon
2020-09-08 12:06 ` Ferruh Yigit
2020-09-11 12:22 ` Thomas Monjalon
2020-09-11 15:54 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2020-09-11 16:22 ` Ferruh Yigit
2020-09-12 8:55 ` Thomas Monjalon
2020-09-14 9:47 ` Ferruh Yigit
2020-09-24 5:41 ` Stephen Hemminger
2020-10-05 8:57 ` Thomas Monjalon [this message]
2020-10-05 9:11 ` Maxime Coquelin
2020-10-05 9:56 ` Bruce Richardson
2020-10-10 7:23 ` 谢华伟(此时此刻）
2020-10-05 9:38 ` [dpdk-dev] [PATCH v3] " Thomas Monjalon
2020-10-05 9:42 ` [dpdk-dev] [PATCH v4] kernel/linux: " Thomas Monjalon
2020-10-05 10:14 ` Andrew Rybchenko
2020-10-05 11:14 ` Jerin Jacob
2020-10-06 10:16 ` Ferruh Yigit
2020-10-06 10:54 ` Thomas Monjalon
2020-10-06 11:09 ` Ferruh Yigit
2020-10-06 12:49 ` Thomas Monjalon
2020-10-06 12:54 ` Thomas Monjalon
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=9651014.gTjpZimMdh@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=maxime.coquelin@redhat.com \
--cc=stephen@networkplumber.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).