From: Chaoyong He <chaoyong.he@corigine.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: oss-drivers <oss-drivers@corigine.com>,
James Hershaw <james.hershaw@corigine.com>
Subject: RE: [PATCH v4 2/2] app/testpmd: add set dev led on/off command
Date: Thu, 10 Oct 2024 05:52:48 +0000 [thread overview]
Message-ID: <SJ0PR13MB5545C9213FB829A1B03169F09E782@SJ0PR13MB5545.namprd13.prod.outlook.com> (raw)
In-Reply-To: <3bb20a75-cb3b-46d8-bfde-261fb1e521a6@amd.com>
> On 9/18/2024 3:38 AM, Chaoyong He wrote:
> > From: James Hershaw <james.hershaw@corigine.com>
> >
> > Add command to change the state of a controllable LED on an ethdev
> > port to on/off. This is for the purpose of identifying which physical
> > port is associated with an ethdev.
> >
> > Usage:
> > testpmd> set port <port-id> led <on/off>
> >
> > Signed-off-by: James Hershaw <james.hershaw@corigine.com>
> > Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
> > ---
> > app/test-pmd/cmdline.c | 52 +++++++++++++++++++++
> > app/test-pmd/config.c | 20 ++++++++
> > app/test-pmd/testpmd.h | 1 +
> > doc/guides/testpmd_app_ug/testpmd_funcs.rst | 7 +++
> > 4 files changed, 80 insertions(+)
> >
> > diff --git a/app/test-pmd/cmdline.c b/app/test-pmd/cmdline.c index
> > a227d3cdc5..a117a4c2fb 100644
> > --- a/app/test-pmd/cmdline.c
> > +++ b/app/test-pmd/cmdline.c
> > @@ -523,6 +523,10 @@ static void cmd_help_long_parsed(void
> *parsed_result,
> > " user is acknowledging and taking responsibility for"
> > " this risk.\n\n"
> >
> > + "set port (port_id) led (on|off)\n"
> > + " set a controllable LED associated with a certain"
> > + " port on or off.\n\n"
> > +
> >
>
> new command seems added in between some mac related commands
> (excluding new eeprom cmd, assuming it will be moved), as we don't have
> anything related to the led before maybe it can go last.
> Same comment for all updates in this patch, can you please double check the
> order, and put updates in middle of other grouping.
Okay, we will send a new version patch.
next prev parent reply other threads:[~2024-10-10 5:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 6:10 [PATCH 0/2] add two commands for testpmd application Chaoyong He
2024-09-12 6:10 ` [PATCH 1/2] app/testpmd: add support for setting device EEPROM Chaoyong He
2024-09-12 6:10 ` [PATCH 2/2] app/testpmd: add set dev led on/off command Chaoyong He
2024-09-12 6:54 ` [PATCH v2 0/2] add two commands for testpmd application Chaoyong He
2024-09-12 6:54 ` [PATCH v2 1/2] app/testpmd: add support for setting device EEPROM Chaoyong He
2024-09-12 9:05 ` fengchengwen
2024-09-13 10:07 ` Chaoyong He
2024-09-12 6:54 ` [PATCH v2 2/2] app/testpmd: add set dev led on/off command Chaoyong He
2024-09-12 8:38 ` fengchengwen
2024-09-13 10:06 ` Chaoyong He
2024-09-14 1:49 ` [PATCH v3 0/2] add two commands for testpmd application Chaoyong He
2024-09-14 1:49 ` [PATCH v3 1/2] app/testpmd: add support for setting device EEPROM Chaoyong He
2024-09-14 7:50 ` fengchengwen
2024-09-14 1:49 ` [PATCH v3 2/2] app/testpmd: add set dev led on/off command Chaoyong He
2024-09-14 7:27 ` fengchengwen
2024-09-18 2:38 ` [PATCH v4 0/2] add two commands for testpmd application Chaoyong He
2024-09-18 2:38 ` [PATCH v4 1/2] app/testpmd: add support for setting device EEPROM Chaoyong He
2024-09-29 22:45 ` Ferruh Yigit
2024-10-10 5:55 ` Chaoyong He
2024-09-18 2:38 ` [PATCH v4 2/2] app/testpmd: add set dev led on/off command Chaoyong He
2024-09-29 22:51 ` Ferruh Yigit
2024-10-10 5:52 ` Chaoyong He [this message]
2024-10-10 6:42 ` [PATCH v5 0/2] add two commands for testpmd application Chaoyong He
2024-10-10 6:42 ` [PATCH v5 1/2] app/testpmd: add support for setting device EEPROM Chaoyong He
2024-10-10 6:42 ` [PATCH v5 2/2] app/testpmd: add set dev led on/off command Chaoyong He
2024-10-12 1:28 ` [PATCH v5 0/2] add two commands for testpmd application Ferruh Yigit
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=SJ0PR13MB5545C9213FB829A1B03169F09E782@SJ0PR13MB5545.namprd13.prod.outlook.com \
--to=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=james.hershaw@corigine.com \
--cc=oss-drivers@corigine.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).