From: Patrick Robb <probb@iol.unh.edu>
To: Andrew Bailey <abailey@iol.unh.edu>
Cc: luca.vizzarro@arm.com, dmarx@iol.unh.edu, dev@dpdk.org
Subject: Re: [PATCH v2] dts: show missing NIC capabilities in DTS logs
Date: Mon, 15 Dec 2025 16:16:25 -0500 [thread overview]
Message-ID: <CAJvnSUDKrsNiQLj1q4mpEiPb6CXRr_9kpb1__qX7Mo-b2O1SiQ@mail.gmail.com> (raw)
In-Reply-To: <20251215183658.674252-1-abailey@iol.unh.edu>
[-- Attachment #1: Type: text/plain, Size: 244 bytes --]
Looks good, thanks Andrew. If it is simple for you to see the commit
which caused this regression, can you include the hash in a "fixes: <hash>"
as is described in the DPDK contributor guidelines?
Reviewed-by: Patrick Robb <probb@iol.unh.edu>
[-- Attachment #2: Type: text/html, Size: 375 bytes --]
next prev parent reply other threads:[~2025-12-15 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 21:01 [PATCH v1] " Andrew Bailey
2025-12-15 18:36 ` [PATCH v2] " Andrew Bailey
2025-12-15 21:16 ` Patrick Robb [this message]
2025-12-15 21:40 ` [PATCH v3] " Andrew Bailey
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=CAJvnSUDKrsNiQLj1q4mpEiPb6CXRr_9kpb1__qX7Mo-b2O1SiQ@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=abailey@iol.unh.edu \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=luca.vizzarro@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).