From: Andrew Bailey <abailey@iol.unh.edu>
To: Patrick Robb <probb@iol.unh.edu>
Cc: luca.vizzarro@arm.com, dev@dpdk.org, thomas@monjalon.net,
david.marchand@redhat.com
Subject: Re: [PATCH 2/2] dts: shorten a too long line
Date: Tue, 18 Nov 2025 09:34:35 -0500 [thread overview]
Message-ID: <CABJ3N2UFwzUi+iuX3+HM9du1CO7riNNVj0M5FMy5YUR-gmbNQw@mail.gmail.com> (raw)
In-Reply-To: <20251113232954.273454-3-probb@iol.unh.edu>
[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]
Reviewed-by: Andrew Bailey <abailey@iol.unh.edu>
On Thu, Nov 13, 2025 at 6:31 PM Patrick Robb <probb@iol.unh.edu> wrote:
> Bring a line which is too long under 100 characters, which
> is the limit.
>
> Fixes: f6fb8c6238db ("dts: add link check on testpmd port start")
>
> Signed-off-by: Patrick Robb <probb@iol.unh.edu>
> ---
> dts/api/testpmd/__init__.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/dts/api/testpmd/__init__.py b/dts/api/testpmd/__init__.py
> index b6f5a8f0da..e98f882b14 100644
> --- a/dts/api/testpmd/__init__.py
> +++ b/dts/api/testpmd/__init__.py
> @@ -96,7 +96,7 @@ def _requires_started_ports(func: TestPmdMethod) ->
> TestPmdMethod:
> func: The :class:`TestPmd` method to decorate.
>
> Raises:
> - InteractiveCommandExecutionError: If the ports has been started
> but a port link will not come up.
> + InteractiveCommandExecutionError: If ports have been started but
> the link won't come up.
> """
>
> @functools.wraps(func)
> --
> 2.49.0
>
>
[-- Attachment #2: Type: text/html, Size: 1595 bytes --]
prev parent reply other threads:[~2025-11-18 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 23:29 [PATCH 0/2] Small formatting issue fixes in DTS Patrick Robb
2025-11-13 23:29 ` [PATCH 1/2] dts: fix incorrect import order for RSS testsuite Patrick Robb
2025-11-18 14:34 ` Andrew Bailey
2025-11-13 23:29 ` [PATCH 2/2] dts: shorten a too long line Patrick Robb
2025-11-18 14:34 ` Andrew Bailey [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=CABJ3N2UFwzUi+iuX3+HM9du1CO7riNNVj0M5FMy5YUR-gmbNQw@mail.gmail.com \
--to=abailey@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=luca.vizzarro@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).