From: "Walsh, Conor" <conor.walsh@intel.com>
To: Ray Kinsella <mdr@ashroe.eu>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"aaron.conole@redhat.com" <aaron.conole@redhat.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: fix CI typo warnings
Date: Thu, 28 Oct 2021 13:50:43 +0000 [thread overview]
Message-ID: <PH0PR11MB5207C8DB60D247650F0E25BBFF869@PH0PR11MB5207.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210810143420.990875-1-mdr@ashroe.eu>
> From: dev <dev-bounces@dpdk.org> On Behalf Of Ray Kinsella
> Sent: Tuesday 10 August 2021 15:34
> To: dev@dpdk.org
> Cc: Richardson, Bruce <bruce.richardson@intel.com>; Mcnamara, John
> <john.mcnamara@intel.com>; aaron.conole@redhat.com; mdr@ashroe.eu
> Subject: [dpdk-dev] [PATCH v2] doc: fix CI typo warnings
>
> Fix documentation typos that are generating spurious CI warnings.
>
> Signed-off-by: Ray Kinsella <mdr@ashroe.eu>
> ---
ioatfwd.c has moved to dmafwd.c but this patch still seems to apply correctly anyway.
Reviewed-by: Conor Walsh <conor.walsh@intel.com>
next prev parent reply other threads:[~2021-10-28 13:50 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
2021-08-31 15:09 ` Kinsella, Ray
2021-10-28 13:50 ` Walsh, Conor [this message]
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=PH0PR11MB5207C8DB60D247650F0E25BBFF869@PH0PR11MB5207.namprd11.prod.outlook.com \
--to=conor.walsh@intel.com \
--cc=aaron.conole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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).