DPDK patches and discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: Nicholas Pratte <npratte@iol.unh.edu>
Cc: yoan.picchi@foss.arm.com, thomas@monjalon.net,
	luca.vizzarro@arm.com,  dmarx@iol.unh.edu,
	paul.szczepanek@arm.com, stephen@networkplumber.org,
	 ian.stokes@intel.com, thomas.wilks@arm.com,
	Honnappa.Nagarahalli@arm.com,  dev@dpdk.org,
	Alex Chapman <alex.chapman@arm.com>
Subject: Re: [PATCH v2 2/2] dts: add mtu update and jumbo frames test suite
Date: Sun, 26 Jan 2025 22:33:28 -0500	[thread overview]
Message-ID: <CAJvnSUAav8kmexN2A1s0AAPEfeH-A+5uCxO53YvY1Le6ZVZj2Q@mail.gmail.com> (raw)
In-Reply-To: <20250124204433.311809-3-npratte@iol.unh.edu>

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

Thanks Nick - A couple minor changes I reduced the testsuite name to simply
"mtu" based on our chat on Friday, and touched up the commit message.

Applied to next-dts.

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

      reply	other threads:[~2025-01-27  3:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-17 14:58 [PATCH v1 0/2] dts: " Nicholas Pratte
2025-01-17 14:58 ` [PATCH v1 1/2] dts: add fwd restart decorator to rx capabilities Nicholas Pratte
2025-01-20  1:11   ` Patrick Robb
2025-01-24 19:35     ` Nicholas Pratte
2025-01-17 14:58 ` [PATCH v1 2/2] dts: add mtu update and jumbo frames test suite Nicholas Pratte
2025-01-20  1:47   ` Patrick Robb
2025-01-24 20:33     ` Nicholas Pratte
2025-01-24 20:44 ` [PATCH v2 0/2] dts: " Nicholas Pratte
2025-01-24 20:44   ` [PATCH v2 1/2] dts: add fwd restart decorator to rx capabilities Nicholas Pratte
2025-01-27  3:31     ` Patrick Robb
2025-01-24 20:44   ` [PATCH v2 2/2] dts: add mtu update and jumbo frames test suite Nicholas Pratte
2025-01-27  3:33     ` Patrick Robb [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=CAJvnSUAav8kmexN2A1s0AAPEfeH-A+5uCxO53YvY1Le6ZVZj2Q@mail.gmail.com \
    --to=probb@iol.unh.edu \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=alex.chapman@arm.com \
    --cc=dev@dpdk.org \
    --cc=dmarx@iol.unh.edu \
    --cc=ian.stokes@intel.com \
    --cc=luca.vizzarro@arm.com \
    --cc=npratte@iol.unh.edu \
    --cc=paul.szczepanek@arm.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas.wilks@arm.com \
    --cc=thomas@monjalon.net \
    --cc=yoan.picchi@foss.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).