From: "Xu, Rosen" <rosen.xu@intel.com>
To: David Marchand <david.marchand@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Zhang, Tianfei" <tianfei.zhang@intel.com>,
"Huang, Wei" <wei.huang@intel.com>
Cc: Ray Kinsella <mdr@ashroe.eu>
Subject: RE: [PATCH] doc: announce some raw/ifpga API removal
Date: Fri, 1 Jul 2022 06:15:48 +0000 [thread overview]
Message-ID: <DM6PR11MB4252327EC6E2A0B1375291A289BD9@DM6PR11MB4252.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220630094129.2066164-1-david.marchand@redhat.com>
Hi David,
Got, thank you so much.
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Thursday, June 30, 2022 17:41
> To: dev@dpdk.org; Xu, Rosen <rosen.xu@intel.com>; Zhang, Tianfei
> <tianfei.zhang@intel.com>
> Cc: Ray Kinsella <mdr@ashroe.eu>
> Subject: [PATCH] doc: announce some raw/ifpga API removal
>
> rte_pmd_ifpga_get_pci_bus() documentation is vague and it is unclear what
> could be done with it.
> On the other hand, EAL provides a standard API to retrieve a bus object by
> name.
>
> Announce removal of this driver specific API for v22.11.
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> A RFC series of the intended changes is available at:
> https://patches.dpdk.org/project/dpdk/list/?series=23811&state=%2A&arch
> ive=both
>
> ---
> doc/guides/rel_notes/deprecation.rst | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> index 4e5b23c53d..64d649777a 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -119,6 +119,8 @@ Deprecation Notices
> * metrics: The function ``rte_metrics_init`` will have a non-void return
> in order to notify errors instead of calling ``rte_exit``.
>
> +* raw/ifgpa: The ``rte_pmd_ifpga_get_pci_bus`` will be removed in 22.11.
> +
> * raw/ioat: The ``ioat`` rawdev driver has been deprecated, since it's
> functionality is provided through the new ``dmadev`` infrastructure.
> To continue to use hardware previously supported by the ``ioat`` rawdev
> driver,
> --
> 2.36.1
next prev parent reply other threads:[~2022-07-01 6:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 9:41 David Marchand
2022-07-01 6:15 ` Xu, Rosen [this message]
2022-07-01 6:25 ` Huang, Wei
2022-07-01 7:00 ` David Marchand
2022-07-01 7:16 ` Huang, Wei
2022-07-01 7:21 ` David Marchand
2022-07-01 8:02 ` Huang, Wei
2022-07-01 8:09 ` David Marchand
2022-07-01 8:14 ` David Marchand
2022-07-01 8:32 ` Huang, Wei
2022-07-01 8:35 ` David Marchand
2022-07-07 9:29 ` David Marchand
2022-07-07 9:34 ` Huang, Wei
2022-07-12 14:24 ` Thomas Monjalon
2022-07-12 15:33 ` Maxime Coquelin
2022-07-16 16:56 ` 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=DM6PR11MB4252327EC6E2A0B1375291A289BD9@DM6PR11MB4252.namprd11.prod.outlook.com \
--to=rosen.xu@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=mdr@ashroe.eu \
--cc=tianfei.zhang@intel.com \
--cc=wei.huang@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;
as well as URLs for NNTP newsgroup(s).