From: Aaron Conole <aconole@redhat.com>
To: Ray Kinsella <mdr@ashroe.eu>
Cc: dev@dpdk.org, bruce.richardson@intel.com,
john.mcnamara@intel.com, Lijuan Tu <lijuan.tu@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: fix CI typo warnings
Date: Mon, 23 Aug 2021 11:18:31 -0400 [thread overview]
Message-ID: <f7tmtp8fauw.fsf@redhat.com> (raw)
In-Reply-To: <20210810143420.990875-1-mdr@ashroe.eu> (Ray Kinsella's message of "Tue, 10 Aug 2021 15:34:20 +0100")
Ray Kinsella <mdr@ashroe.eu> writes:
> Fix documentation typos that are generating spurious CI warnings.
>
> Signed-off-by: Ray Kinsella <mdr@ashroe.eu>
> ---
> v2:
> * Fix some additional typos pointed out by Aaron Conole
>
> doc/guides/rel_notes/deprecation.rst | 4 ++--
> doc/guides/sample_app_ug/ioat.rst | 2 +-
> doc/guides/sample_app_ug/vmdq_forwarding.rst | 2 +-
> examples/ioat/ioatfwd.c | 2 +-
> examples/vmdq/main.c | 2 +-
> 5 files changed, 6 insertions(+), 6 deletions(-)
>
LGTM. I noticed that the Intel environment flagged a sphinx in the vmdq
change, but no other environment did.
Lijuan, can you help understand why this happened?
Acked-by: Aaron Conole <aconole@redhat.com>
next prev parent reply other threads:[~2021-08-23 15:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 13:06 [dpdk-dev] [PATCH v1] " Ray Kinsella
2021-08-09 14:43 ` Aaron Conole
2021-08-10 13:59 ` Kinsella, Ray
2021-08-10 14:34 ` [dpdk-dev] [PATCH v2] " Ray Kinsella
2021-08-23 15:18 ` Aaron Conole [this message]
2021-08-31 15:09 ` Kinsella, Ray
2021-10-28 13:50 ` Walsh, Conor
2021-11-26 13:18 ` David Marchand
2021-11-26 13:34 ` David Marchand
2021-11-26 13:37 ` Kinsella, Ray
2021-11-26 13:44 ` 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=f7tmtp8fauw.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=lijuan.tu@intel.com \
--cc=mdr@ashroe.eu \
/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).