From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Shepard Siegel <shepard.siegel@atomicrules.com>,
ed.czeck@atomicrules.com
Cc: dev@dpdk.org
Subject: Re: [PATCH 1/2] doc: clarify the existing net/ark guide
Date: Mon, 13 Feb 2023 23:39:48 +0000 [thread overview]
Message-ID: <61ca1e57-93d7-c790-7c90-2a5dab630495@amd.com> (raw)
In-Reply-To: <20230213195825.2934483-1-shepard.siegel@atomicrules.com>
On 2/13/2023 7:58 PM, Shepard Siegel wrote:
> Add detail for the existing Arkville configurations FX0 and FX1.
> Corrected minor errors of omission.
>
> Signed-off-by: Shepard Siegel <shepard.siegel@atomicrules.com>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-02-13 23:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 14:14 [PATCH 1/2] net/ark: add new device to PCIe allowlist Shepard Siegel
2023-02-11 14:14 ` [PATCH 2/2] doc: update ark guide to include new PCIe device Shepard Siegel
2023-02-13 13:46 ` [PATCH 1/2] net/ark: add new device to PCIe allowlist Ferruh Yigit
2023-02-13 15:02 ` Shepard Siegel
2023-02-13 14:58 ` [PATCH 1/4] doc: clarify the existing net/ark guide Shepard Siegel
2023-02-13 14:58 ` [PATCH 2/4] net/ark: add new device to PCIe allowlist Shepard Siegel
2023-02-13 15:51 ` Ferruh Yigit
2023-02-13 17:12 ` Shepard Siegel
2023-02-13 14:58 ` [PATCH 3/4] doc: update ark guide to include new PCIe device Shepard Siegel
2023-02-13 14:58 ` [PATCH 4/4] doc: update Release Notes Shepard Siegel
2023-02-13 15:46 ` [PATCH 1/4] doc: clarify the existing net/ark guide Ferruh Yigit
2023-02-13 17:09 ` Shepard Siegel
2023-02-13 17:23 ` Ferruh Yigit
2023-02-13 17:31 ` Shepard Siegel
2023-02-13 22:58 ` Ferruh Yigit
2023-02-13 19:58 ` [PATCH 1/2] " Shepard Siegel
2023-02-13 19:58 ` [PATCH 2/2] net/ark: add new ark PCIe device Shepard Siegel
2023-02-13 23:39 ` Ferruh Yigit
2023-02-13 23:39 ` Ferruh Yigit [this message]
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=61ca1e57-93d7-c790-7c90-2a5dab630495@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=ed.czeck@atomicrules.com \
--cc=shepard.siegel@atomicrules.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).