From: Nicholas Pratte <npratte@iol.unh.edu>
To: Luca Vizzarro <Luca.Vizzarro@arm.com>
Cc: dev@dpdk.org, "Juraj Linkeš" <juraj.linkes@pantheon.tech>,
"Jeremy Spewock" <jspewock@iol.unh.edu>
Subject: Re: [PATCH v2 0/2] dts: update mypy and clean up
Date: Fri, 24 May 2024 09:47:21 -0400 [thread overview]
Message-ID: <CAKXZ7ejiuiYzUZYvGjyuJfvm5CgvDfFnhnQLEx3qsc-eLAaxNQ@mail.gmail.com> (raw)
In-Reply-To: <f6fd2176-4dce-41f1-9749-04f84e1fe7a8@arm.com>
Disregard that last comment, it was a mistake on my end. Updating the
dependencies in my container instance fixed the problem.
On Tue, May 21, 2024 at 10:59 AM Luca Vizzarro <Luca.Vizzarro@arm.com> wrote:
>
> On 20/05/2024 16:37, Nicholas Pratte wrote:
> > Ran into no issues with this when testing your port stats and info
> > patch, so I'll provide a tested tag as well. Other than a couple of
> > issues listed in dts-check-format, everything looks good.
>
> This patch series should address all of the issues in
> dts-check-format... what issues are you seeing?
>
next prev parent reply other threads:[~2024-05-24 13:47 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 10:57 [PATCH " Luca Vizzarro
2024-05-09 10:57 ` [PATCH 1/2] dts: update mypy static checker Luca Vizzarro
2024-05-13 16:02 ` Juraj Linkeš
2024-05-14 11:30 ` Luca Vizzarro
2024-05-29 11:22 ` Juraj Linkeš
2024-05-09 10:57 ` [PATCH 2/2] dts: clean up config types Luca Vizzarro
2024-05-13 16:12 ` Juraj Linkeš
2024-05-14 11:30 ` Luca Vizzarro
2024-05-29 11:41 ` Juraj Linkeš
2024-05-14 11:34 ` [PATCH v2 0/2] dts: update mypy and clean up Luca Vizzarro
2024-05-14 11:34 ` [PATCH v2 1/2] dts: update mypy static checker Luca Vizzarro
2024-05-24 14:51 ` Patrick Robb
2024-05-28 12:00 ` Luca Vizzarro
2024-05-29 10:58 ` Juraj Linkeš
2024-05-29 11:39 ` Juraj Linkeš
2024-05-29 15:20 ` Luca Vizzarro
2024-05-14 11:34 ` [PATCH v2 2/2] dts: clean up config types Luca Vizzarro
2024-05-24 16:13 ` Patrick Robb
2024-05-20 15:37 ` [PATCH v2 0/2] dts: update mypy and clean up Nicholas Pratte
2024-05-21 14:59 ` Luca Vizzarro
2024-05-24 13:47 ` Nicholas Pratte [this message]
2024-05-24 16:17 ` Patrick Robb
2024-05-28 12:05 ` Luca Vizzarro
2024-05-29 10:44 ` Juraj Linkeš
2024-05-30 15:19 ` [PATCH v3 " Luca Vizzarro
2024-05-30 15:19 ` [PATCH v3 1/2] dts: update mypy static checker Luca Vizzarro
2024-05-30 20:23 ` Jeremy Spewock
2024-05-31 9:29 ` Juraj Linkeš
2024-06-17 15:28 ` Nicholas Pratte
2024-05-30 15:19 ` [PATCH v3 2/2] dts: clean up config types Luca Vizzarro
2024-05-30 20:23 ` Jeremy Spewock
2024-05-31 9:29 ` Juraj Linkeš
2024-06-17 15:30 ` Nicholas Pratte
2024-06-19 23:02 ` [PATCH v3 0/2] dts: update mypy and clean up Thomas Monjalon
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=CAKXZ7ejiuiYzUZYvGjyuJfvm5CgvDfFnhnQLEx3qsc-eLAaxNQ@mail.gmail.com \
--to=npratte@iol.unh.edu \
--cc=Luca.Vizzarro@arm.com \
--cc=dev@dpdk.org \
--cc=jspewock@iol.unh.edu \
--cc=juraj.linkes@pantheon.tech \
/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).