DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@oss.nxp.com>
To: Gagandeep Singh <g.singh@nxp.com>,
	thomas@monjalon.net, dev@dpdk.org, hemant.agrawal@nxp.com
Subject: Re: [PATCH] doc: notice to deprecate DPAA2 cmdif raw driver
Date: Wed, 29 Jun 2022 11:53:40 +0530	[thread overview]
Message-ID: <e709208a-dd9f-3a11-efb1-4f2725895592@oss.nxp.com> (raw)
In-Reply-To: <20220629043804.3280057-1-g.singh@nxp.com>

Acked-by:  Hemant Agrawal <hemant.agrawal@nxp.com>

On 6/29/2022 10:08 AM, Gagandeep Singh wrote:
> dpaa2_cmdif raw driver is no longer in use, so it
> will be removed in v22.11
>
> Signed-off-by: Gagandeep Singh <g.singh@nxp.com>
> ---
>   doc/guides/rel_notes/deprecation.rst | 3 +++
>   1 file changed, 3 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index 4e5b23c53d..d279fcc99b 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -125,3 +125,6 @@ Deprecation Notices
>     applications should be updated to use the ``dmadev`` library instead,
>     with the underlying HW-functionality being provided by the ``ioat`` or
>     ``idxd`` dma drivers
> +
> +* raw/dpaa2_cmdif/: The ``dpaa2_cmdif`` rawdev driver will be deprecated
> +  in 22.11, as it is no longer in use, no active user known.

  reply	other threads:[~2022-06-29  6:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29  4:38 Gagandeep Singh
2022-06-29  6:23 ` Hemant Agrawal [this message]
2022-07-12 14:29   ` Thomas Monjalon
2022-07-12 14:46     ` Bruce Richardson
2022-07-16 16:39 ` 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=e709208a-dd9f-3a11-efb1-4f2725895592@oss.nxp.com \
    --to=hemant.agrawal@oss.nxp.com \
    --cc=dev@dpdk.org \
    --cc=g.singh@nxp.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=thomas@monjalon.net \
    /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).