DPDK patches and discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: Andrew Bailey <abailey@iol.unh.edu>
Cc: luca.vizzarro@arm.com, dev@dpdk.org, dmarx@iol.unh.edu
Subject: Re: [PATCH v3] dts: enable port binding on the TG
Date: Thu, 28 Aug 2025 08:54:26 -0400	[thread overview]
Message-ID: <CAJvnSUDGvKb-bP3Zpk8=vciAf_9V4WP9S3UpSgGVKYJy1oOm0Q@mail.gmail.com> (raw)
In-Reply-To: <20250828123758.20451-1-abailey@iol.unh.edu>

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

Thanks Luca for the patch submission best practices advice. :)

Andrew we can chat more about the bound_for_dpdk() at the DTS meeting.

On Thu, Aug 28, 2025 at 8:38 AM Andrew Bailey <abailey@iol.unh.edu> wrote:

>
> +        ctx = get_ctx()
> +        prepare_node(ctx.tg_node)
> +        prepare_node(ctx.sut_node)
> +        # ctx.tg_node.main_session.bring_up_link(self.sut_ports)
>

Make sure to drop these commented out function calls and such when you
submit.


> +
>      @property
>      def sut_dpdk_ports(self) -> list[Port]:
>          """The DPDK ports for the SUT node."""
> --
> 2.50.1
>
>
Thanks Andrew.

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

  parent reply	other threads:[~2025-08-28 13:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-08 18:21 [PATCH 1/2] dts: introduce abstract class for TG and SUT DPDK runtime environments Andrew Bailey
2025-08-08 18:21 ` [PATCH 2/2] dts: enable port binding on the TG Andrew Bailey
2025-08-28 12:37   ` [PATCH v3] " Andrew Bailey
2025-08-28 12:50     ` Luca Vizzarro
2025-08-28 15:17       ` Andrew Bailey
2025-08-28 12:54     ` Patrick Robb [this message]
2025-08-11 11:17 ` [PATCH 1/2] dts: introduce abstract class for TG and SUT DPDK runtime environments Luca Vizzarro

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='CAJvnSUDGvKb-bP3Zpk8=vciAf_9V4WP9S3UpSgGVKYJy1oOm0Q@mail.gmail.com' \
    --to=probb@iol.unh.edu \
    --cc=abailey@iol.unh.edu \
    --cc=dev@dpdk.org \
    --cc=dmarx@iol.unh.edu \
    --cc=luca.vizzarro@arm.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).