From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: jspewock@iol.unh.edu, thomas@monjalon.net, alex.chapman@arm.com,
Luca.Vizzarro@arm.com, yoan.picchi@foss.arm.com,
paul.szczepanek@arm.com, probb@iol.unh.edu,
Honnappa.Nagarahalli@arm.com, wathsala.vithanage@arm.com,
npratte@iol.unh.edu
Cc: dev@dpdk.org
Subject: Re: [PATCH v4 0/1] dts: allow for updating MTU with testpmd
Date: Mon, 9 Sep 2024 17:52:21 +0200 [thread overview]
Message-ID: <425ac703-8dce-464d-9eb6-52e7cdb5bf75@pantheon.tech> (raw)
In-Reply-To: <20240906180036.19446-1-jspewock@iol.unh.edu>
Applied to next-dts, thanks.
On 6. 9. 2024 20:00, jspewock@iol.unh.edu wrote:
> From: Jeremy Spewock <jspewock@iol.unh.edu>
>
> v4:
> * add dependency on port caching patch to avoid the need for
> the if-statement that was added in the last version.
>
> Jeremy Spewock (1):
> dts: add methods for modifying MTU to testpmd shell
>
> dts/framework/remote_session/testpmd_shell.py | 44 +++++++++++++++++++
> 1 file changed, 44 insertions(+)
>
prev parent reply other threads:[~2024-09-09 15:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 20:02 [PATCH v1 " jspewock
2024-08-26 20:02 ` [PATCH v1 1/1] dts: add methods for modifying MTU to testpmd shell jspewock
2024-08-26 21:13 ` [PATCH v2 0/1] dts: allow for updating MTU with testpmd jspewock
2024-08-26 21:13 ` [PATCH v2 1/1] dts: add methods for modifying MTU to testpmd shell jspewock
2024-09-05 14:21 ` [PATCH v3 0/1] dts: allow for updating MTU with testpmd jspewock
2024-09-05 14:21 ` [PATCH v3 1/1] dts: add methods for modifying MTU to testpmd shell jspewock
2024-09-06 13:58 ` Juraj Linkeš
2024-09-06 14:28 ` Jeremy Spewock
2024-09-06 18:00 ` [PATCH v4 0/1] dts: allow for updating MTU with testpmd jspewock
2024-09-06 18:00 ` [PATCH v4 1/1] dts: add methods for modifying MTU to testpmd shell jspewock
2024-09-09 12:32 ` Luca Vizzarro
2024-09-09 12:33 ` Luca Vizzarro
2024-09-09 15:52 ` Juraj Linkeš [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=425ac703-8dce-464d-9eb6-52e7cdb5bf75@pantheon.tech \
--to=juraj.linkes@pantheon.tech \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Luca.Vizzarro@arm.com \
--cc=alex.chapman@arm.com \
--cc=dev@dpdk.org \
--cc=jspewock@iol.unh.edu \
--cc=npratte@iol.unh.edu \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
--cc=wathsala.vithanage@arm.com \
--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).