From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: thomas@monjalon.net, Honnappa.Nagarahalli@arm.com,
paul.szczepanek@arm.com, Luca.Vizzarro@arm.com,
alex.chapman@arm.com, probb@iol.unh.edu, jspewock@iol.unh.edu,
npratte@iol.unh.edu, dmarx@iol.unh.edu
Cc: dev@dpdk.org
Subject: Re: [PATCH v1] dts: fix testpmd port device error handling mode
Date: Mon, 9 Sep 2024 17:51:09 +0200 [thread overview]
Message-ID: <f51c4fe4-baf6-4764-b5a1-c19cc8cd21ca@pantheon.tech> (raw)
In-Reply-To: <20240823074553.15815-1-juraj.linkes@pantheon.tech>
Applied to next-dts, thanks.
On 23. 8. 2024 9:45, Juraj Linkeš wrote:
> Make device_error_handling_mode of testpmd port optional as it may not
> be present, e.g. in VM ports.
>
> Fixes: 61d5bc9bf974 ("dts: add port info command to testpmd shell")
>
> Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
> ---
> dts/framework/remote_session/testpmd_shell.py | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/dts/framework/remote_session/testpmd_shell.py b/dts/framework/remote_session/testpmd_shell.py
> index 43e9f56517..c3df44e7ab 100644
> --- a/dts/framework/remote_session/testpmd_shell.py
> +++ b/dts/framework/remote_session/testpmd_shell.py
> @@ -464,8 +464,8 @@ class TestPmdPort(TextParser):
> metadata=DeviceCapabilitiesFlag.make_parser(),
> )
> #:
> - device_error_handling_mode: DeviceErrorHandlingMode = field(
> - metadata=DeviceErrorHandlingMode.make_parser()
> + device_error_handling_mode: DeviceErrorHandlingMode | None = field(
> + default=None, metadata=DeviceErrorHandlingMode.make_parser()
> )
> #:
> device_private_info: str | None = field(
prev parent reply other threads:[~2024-09-09 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 7:45 Juraj Linkeš
2024-09-02 13:46 ` Luca Vizzarro
2024-09-05 16:10 ` Jeremy Spewock
2024-09-09 15:51 ` 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=f51c4fe4-baf6-4764-b5a1-c19cc8cd21ca@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=dmarx@iol.unh.edu \
--cc=jspewock@iol.unh.edu \
--cc=npratte@iol.unh.edu \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
/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).