From: jspewock@iol.unh.edu
To: alex.chapman@arm.com, npratte@iol.unh.edu, thomas@monjalon.net,
Honnappa.Nagarahalli@arm.com, juraj.linkes@pantheon.tech,
probb@iol.unh.edu, yoan.picchi@foss.arm.com,
Luca.Vizzarro@arm.com, paul.szczepanek@arm.com,
wathsala.vithanage@arm.com
Cc: dev@dpdk.org, Jeremy Spewock <jspewock@iol.unh.edu>
Subject: [PATCH v2 0/1] dts: add driver binding on TG
Date: Thu, 19 Sep 2024 14:16:10 -0400 [thread overview]
Message-ID: <20240919181611.20289-1-jspewock@iol.unh.edu> (raw)
In-Reply-To: <20240812172251.41131-1-jspewock@iol.unh.edu>
From: Jeremy Spewock <jspewock@iol.unh.edu>
v2:
* only copy the devbind script onto the TG node rather than the
entire DPDK directory
Jeremy Spewock (1):
dts: add binding to different drivers to TG node
dts/framework/runner.py | 2 +
dts/framework/testbed_model/node.py | 49 ++++++++++++++++++++++++-
dts/framework/testbed_model/sut_node.py | 39 ++++++--------------
dts/framework/testbed_model/tg_node.py | 21 +++++++++++
dts/framework/utils.py | 4 +-
5 files changed, 85 insertions(+), 30 deletions(-)
--
2.46.0
--
*Let's Connect!*
... *October Webinars*
Ask Us Anything: IOL Services
Open Q&A
<https://unh.zoom.us/webinar/register/9017265932716/WN_OUo5S7iQRLmKKY7CsmwZhw#/registration>Your
questions. Our answers. Let's get started.
Oct 3rd
Live Tour of INTACT(R)
for IPv6 Testing and Validation
<https://unh.zoom.us/webinar/register/7117231236474/WN_I2zfyi_2S2yEiXkxBRi8sA#/registration>
Open tour. Open Q&A. See why we think you'll love INTACT.
Oct 9th
How to
Prep for Our NVMe(R) Plugfest #21
<https://unh.zoom.us/webinar/register/4017266809553/WN_X1iA2SZ8QhmcGboF2DImNg#/registration>
Checklists. Conversation. Let's get ready to plugin!
Oct 15th
... *
Newsletter*
*
*
Get the IOL Connector
<https://www.iol.unh.edu/news/email-newsletters> for our latest news and
event info.
.
next prev parent reply other threads:[~2024-09-19 18:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 17:22 [PATCH " jspewock
2024-08-12 17:22 ` [PATCH 1/1] dts: add binding to different drivers to TG node jspewock
2024-08-12 17:49 ` Nicholas Pratte
2024-09-09 12:16 ` Juraj Linkeš
2024-09-09 15:55 ` Jeremy Spewock
2024-09-16 10:04 ` Juraj Linkeš
2024-09-18 18:50 ` Jeremy Spewock
2024-09-19 9:10 ` Juraj Linkeš
2024-09-12 13:00 ` Patrick Robb
2024-09-19 18:16 ` jspewock [this message]
2024-09-19 18:16 ` [PATCH v2 " jspewock
2024-09-24 9:12 ` Juraj Linkeš
2024-09-24 13:57 ` Jeremy Spewock
2024-09-24 14:03 ` Juraj Linkeš
2024-09-24 16:28 ` [PATCH v3 0/2] dts: add driver binding on TG jspewock
2024-09-24 16:28 ` [PATCH v3 1/2] dts: add symbolic link to dpdk-devbind script jspewock
2024-09-25 5:48 ` Juraj Linkeš
2024-09-27 11:49 ` Luca Vizzarro
2024-09-24 16:28 ` [PATCH v3 2/2] dts: add binding to different drivers to TG node jspewock
2024-09-25 6:01 ` Juraj Linkeš
2024-09-27 11:50 ` Luca Vizzarro
2024-09-30 13:42 ` [PATCH v3 0/2] dts: add driver binding on TG Juraj Linkeš
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=20240919181611.20289-1-jspewock@iol.unh.edu \
--to=jspewock@iol.unh.edu \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Luca.Vizzarro@arm.com \
--cc=alex.chapman@arm.com \
--cc=dev@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--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).