DPDK patches and discussions
 help / color / mirror / Atom feed
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 2/4] net/ark: add new device to PCIe allowlist
Date: Mon, 13 Feb 2023 12:12:18 -0500	[thread overview]
Message-ID: <CAMMLSKC5nM6U4Aq1XeYt_npqSnfWh2phPB31YKR4u8pHg0xtMA@mail.gmail.com> (raw)
In-Reply-To: <2a62f7a3-5c09-036e-eae8-ed992a35ccd2@amd.com>

[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]

Hi Ferruh,

If you dont mind squashing 2/4 3/4 4/4 together, that would be great.

Thank you for correcting on the allowlist, s..b "supported PCIe ids list"
instead.

best, Shep


On Mon, Feb 13, 2023 at 10:51 AM Ferruh Yigit <ferruh.yigit@amd.com> wrote:

> On 2/13/2023 2:58 PM, Shepard Siegel wrote:
> > This patch adds the Arkville FX2 device to the PCIe allowlist.
> >
> > Signed-off-by: Shepard Siegel <shepard.siegel@atomicrules.com>
> > ---
> >  drivers/net/ark/ark_ethdev.c | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/net/ark/ark_ethdev.c b/drivers/net/ark/ark_ethdev.c
> > index c654a229f7..b2995427c8 100644
> > --- a/drivers/net/ark/ark_ethdev.c
> > +++ b/drivers/net/ark/ark_ethdev.c
> > @@ -99,6 +99,7 @@ static const struct rte_pci_id pci_id_ark_map[] = {
> >       {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x101c)},
> >       {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x101e)},
> >       {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x101f)},
> > +     {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x1022)},
> >       {.vendor_id = 0, /* sentinel */ },
> >  };
> >
>
> It is possible to squash 2/4, 3/4 & 4/4 into single patch, I can do it
> while merging.
>
> In the patch title it mentions 'PCIe allowlist', this is not a kind of
> allow list, this is list of PCI ids supported by driver, so I can update
> patch title as following while merging if there won't be a new version:
> "net/ark: support Arkville FX2 device"
>

[-- Attachment #2: Type: text/html, Size: 2058 bytes --]

  reply	other threads:[~2023-02-13 17:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-11 14:14 [PATCH 1/2] " 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 [this message]
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=CAMMLSKC5nM6U4Aq1XeYt_npqSnfWh2phPB31YKR4u8pHg0xtMA@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).