From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: David Marchand <david.marchand@redhat.com>, dev@dpdk.org
Cc: Nicolas Chautru <nicolas.chautru@intel.com>
Subject: Re: [PATCH] doc: fix 22.11 release notes after acc200 driver rename
Date: Tue, 7 Feb 2023 09:27:29 +0100 [thread overview]
Message-ID: <bde0f745-0550-af17-9345-d8cf80f1606c@redhat.com> (raw)
In-Reply-To: <20230207080524.1976354-1-david.marchand@redhat.com>
On 2/7/23 09:05, David Marchand wrote:
> Renaming this driver and its associated doc was not properly handled
> with regard to the previous 22.11 release notes.
As discussed, ninja did not try again to build the release note after
having fixed the initial issue. Forcing its rebuild I could reproduce
the issue.
> Fixes: 5f1565617a9d ("doc: update naming for Intel baseband acc200")
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> doc/guides/rel_notes/release_22_11.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/doc/guides/rel_notes/release_22_11.rst b/doc/guides/rel_notes/release_22_11.rst
> index 7f2bd123f3..91414573bd 100644
> --- a/doc/guides/rel_notes/release_22_11.rst
> +++ b/doc/guides/rel_notes/release_22_11.rst
> @@ -220,8 +220,8 @@ New Features
> * **Added Intel ACC200 bbdev driver.**
>
> Added a new ``acc200`` bbdev driver for the Intel\ |reg| ACC200 accelerator
> - integrated on SPR-EE. See the
> - :doc:`../bbdevs/acc200` guide for more details on this new driver.
> + integrated on SPR-EE. See the ``bbdevs/acc200`` guide for more details
> + on this new driver.
>
> * **Added eventdev adapter instance get API.**
>
Tested-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Thanks,
Maxime
next prev parent reply other threads:[~2023-02-07 8:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 8:05 David Marchand
2023-02-07 8:27 ` Maxime Coquelin [this message]
2023-02-07 8:36 ` David Marchand
2023-02-07 8:37 ` David Marchand
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=bde0f745-0550-af17-9345-d8cf80f1606c@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=nicolas.chautru@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).