From: Shepard Siegel <shepard.siegel@atomicrules.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: ed.czeck@atomicrules.com, dev@dpdk.org
Subject: Re: [PATCH 1/2] net/ark: add new device to PCIe allowlist
Date: Mon, 13 Feb 2023 10:02:06 -0500 [thread overview]
Message-ID: <CAMMLSKD3H5NQM36FEm-AHtmV3FGz=e0PmfRdhRFt8e9uvj77yA@mail.gmail.com> (raw)
In-Reply-To: <239160fe-774e-3861-60e3-2c708849e310@amd.com>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
Thank you Ferruh,
We have rolled all changes, including your suggestion on the Release Note,
into the four distinct patches in this patchset which collectively brings
the
ark PMD up to date for this new capability.
best, Shep
On Mon, Feb 13, 2023 at 8:46 AM Ferruh Yigit <ferruh.yigit@amd.com> wrote:
> On 2/11/2023 2:14 PM, Shepard Siegel wrote:
> > This patch adds the Arkville FX2 device to the PCIe allowlist.
> >
> > Signed-off-by: Shepard Siegel <shepard.siegel@atomicrules.com>
>
> Hi Shepard, Ed,
>
> The patchset looks good, I can squash them into single patch while merging.
>
> I don't know how major this new device is, if it is an important one you
> may want to introduce it in the release notes too, what do think?
>
> And if you will send a new version, can you please put previous doc
> patch [1] and this to the same patchset since this one depends previous
> doc patch to apply cleanly.
>
> Thanks.
>
>
> [1]
> doc: clarify the existing net/ark guide
>
[-- Attachment #2: Type: text/html, Size: 1497 bytes --]
next prev parent reply other threads:[~2023-02-13 15:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 14:14 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 [this message]
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 ` [PATCH 1/2] doc: clarify the existing net/ark guide Ferruh Yigit
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='CAMMLSKD3H5NQM36FEm-AHtmV3FGz=e0PmfRdhRFt8e9uvj77yA@mail.gmail.com' \
--to=shepard.siegel@atomicrules.com \
--cc=dev@dpdk.org \
--cc=ed.czeck@atomicrules.com \
--cc=ferruh.yigit@amd.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).