From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: Huzaifa Rahman <huzaifa.rahman@emumba.com>, <dev@dpdk.org>
Subject: Re: [PATCH v2] ethtool: added help command to list all available
Date: Mon, 30 May 2022 11:42:46 +0100 [thread overview]
Message-ID: <f60f9b7c-6ea0-70ff-3e23-32fc4a4ad9c1@xilinx.com> (raw)
In-Reply-To: <CANVhzTiQx6CatcrYgN9cF58rZNDTaoZbtB9bphhLDQ=jVnAQJQ@mail.gmail.com>
On 5/27/2022 6:14 AM, Huzaifa Rahman wrote:
> [CAUTION: External Email]
> Hi,
>
> The following tests are failing but my patch is not related to anything
> related to these. Please re-run the tests.
>
> Failed Tests:
> - mtu_update
> - scatter
>
Hi Huzaifa,
Agree, it looks unrelated, I will trigger the test again, can please
check in ~10 mins.
>
> Thanks,
>
> Huzaifa
>
>
>
> On Tue, Mar 22, 2022 at 2:36 PM huzaifa.rahman
> <huzaifa.rahman@emumba.com <mailto:huzaifa.rahman@emumba.com>> wrote:
>
> Help command is not available for ethtool example. It is needed so user
> can see all the available commands directly from the command line along
> with the formats.
>
> Signed-off-by: huzaifa.rahman <huzaifa.rahman@emumba.com
> <mailto:huzaifa.rahman@emumba.com>>
> ---
> doc/guides/sample_app_ug/ethtool.rst | 1 +
> examples/ethtool/ethtool-app/ethapp.c | 38 +++++++++++++++++++++++++++
> examples/ethtool/ethtool-app/ethapp.h | 1 +
> 3 files changed, 40 insertions(+)
>
<...>
next prev parent reply other threads:[~2022-05-30 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 14:25 [PATCH] ethtool: added list command to list all available commands huzaifa.rahman
2022-03-22 9:36 ` [PATCH v2] ethtool: added help command to list all available huzaifa.rahman
2022-05-27 5:14 ` Huzaifa Rahman
2022-05-30 10:42 ` Ferruh Yigit [this message]
2022-07-26 11:09 ` Huzaifa Rahman
2023-07-03 22:24 ` [PATCH] ethtool: added list command to list all available commands Stephen Hemminger
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=f60f9b7c-6ea0-70ff-3e23-32fc4a4ad9c1@xilinx.com \
--to=ferruh.yigit@xilinx.com \
--cc=dev@dpdk.org \
--cc=huzaifa.rahman@emumba.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).