From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2] raw/ioat: remove deprecated driver
Date: Wed, 28 Sep 2022 14:42:22 +0200 [thread overview]
Message-ID: <3021960.U7HbjWM52l@thomas> (raw)
In-Reply-To: <20220920155445.480399-1-bruce.richardson@intel.com>
20/09/2022 17:54, Bruce Richardson:
> The ioat driver has been superseded by the ioat and idxd dmadev drivers,
> and has been deprecated for some time, so remove it.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
> V2: remove references to ioat rawdev from API guide
> ---
> doc/api/doxy-api-index.md | 1 -
> doc/api/doxy-api.conf.in | 1 -
> doc/guides/rawdevs/index.rst | 1 -
> doc/guides/rawdevs/ioat.rst | 333 -----------
> doc/guides/rel_notes/deprecation.rst | 7 -
> drivers/raw/ioat/dpdk_idxd_cfg.py | 1 -
> drivers/raw/ioat/idxd_bus.c | 365 ------------
> drivers/raw/ioat/idxd_pci.c | 380 -------------
> drivers/raw/ioat/ioat_common.c | 273 ---------
> drivers/raw/ioat/ioat_private.h | 84 ---
> drivers/raw/ioat/ioat_rawdev.c | 332 -----------
> drivers/raw/ioat/ioat_rawdev_test.c | 734 -------------------------
> drivers/raw/ioat/ioat_spec.h | 336 -----------
> drivers/raw/ioat/meson.build | 36 --
> drivers/raw/ioat/rte_idxd_rawdev_fns.h | 394 -------------
> drivers/raw/ioat/rte_ioat_rawdev.h | 214 -------
> drivers/raw/ioat/rte_ioat_rawdev_fns.h | 379 -------------
> drivers/raw/ioat/version.map | 3 -
> drivers/raw/meson.build | 1 -
> 19 files changed, 3875 deletions(-)
MAINTAINERS update was missing (fixed).
Applied, thanks.
prev parent reply other threads:[~2022-09-28 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 15:14 [PATCH] " Bruce Richardson
2022-09-20 15:54 ` [PATCH v2] " Bruce Richardson
2022-09-28 12:42 ` Thomas Monjalon [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=3021960.U7HbjWM52l@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.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).