From: Patrick Robb <probb@iol.unh.edu>
To: Dean Marx <dmarx@iol.unh.edu>
Cc: luca.vizzarro@arm.com, yoan.picchi@foss.arm.com,
Honnappa.Nagarahalli@arm.com, paul.szczepanek@arm.com,
dev@dpdk.org
Subject: Re: [PATCH v3 1/4] dts: add virtual functions to framework
Date: Mon, 7 Jul 2025 11:31:31 -0400 [thread overview]
Message-ID: <CAJvnSUB=fV6cgkxVsEzdb9ofm9HVN9WxLi3haL8b7=xKgcYUtg@mail.gmail.com> (raw)
In-Reply-To: <CAJvnSUA1PM01oHvsRRt7mru5Tuj-rjMh+hOjR3zG9g1WkD-wrw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 294 bytes --]
FYI based on conversation with Dean I pushed a fixup adding
the use_virtual_functions: false field to the test_run.example.yaml, so
that users can more easily understand how to enable the VF testruns.
https://git.dpdk.org/next/dpdk-next-dts/commit/?id=934206f3bfc10fb8dcd852479f3683c01a18e352
[-- Attachment #2: Type: text/html, Size: 449 bytes --]
next prev parent reply other threads:[~2025-07-07 15:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 20:13 [PATCH v1] " Dean Marx
2025-06-26 15:27 ` [PATCH v2 1/4] " Dean Marx
2025-06-26 15:27 ` [PATCH v2 2/4] dts: remove unnecessary testpmd verification Dean Marx
2025-06-26 15:27 ` [PATCH v2 3/4] dts: modify existing suites to work with VFs Dean Marx
2025-07-02 16:23 ` [PATCH v3 1/4] dts: add virtual functions to framework Dean Marx
2025-07-02 16:23 ` [PATCH v3 2/4] dts: remove unnecessary testpmd verification Dean Marx
2025-07-04 4:23 ` Patrick Robb
2025-07-02 16:23 ` [PATCH v3 3/4] dts: add physical function capability check Dean Marx
2025-07-04 4:23 ` Patrick Robb
2025-07-02 16:23 ` [PATCH v3 4/4] dts: add sr-iov section to docs Dean Marx
2025-07-04 4:23 ` Patrick Robb
2025-07-02 16:48 ` [PATCH v3 1/4] dts: add virtual functions to framework Dean Marx
2025-07-04 4:22 ` Patrick Robb
2025-07-04 4:25 ` Patrick Robb
2025-07-04 19:45 ` Patrick Robb
2025-07-07 15:31 ` Patrick Robb [this message]
2025-06-26 15:27 ` [PATCH v2 4/4] dts: add physical function capability check Dean Marx
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='CAJvnSUB=fV6cgkxVsEzdb9ofm9HVN9WxLi3haL8b7=xKgcYUtg@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=luca.vizzarro@arm.com \
--cc=paul.szczepanek@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).