From: David Marchand <david.marchand@redhat.com>
To: Yogesh Jangra <yogesh.jangra@intel.com>
Cc: dev <dev@dpdk.org>, Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1] examples/pipeline: fix help command
Date: Fri, 23 Oct 2020 13:45:07 +0200 [thread overview]
Message-ID: <CAJFAV8yS94Dd9hgtNRFDgADCVtqV5sGBCr-yVgyo5RXYg-kLPQ@mail.gmail.com> (raw)
In-Reply-To: <1603364512-48824-1-git-send-email-yogesh.jangra@intel.com>
On Thu, Oct 22, 2020 at 1:03 PM Yogesh Jangra <yogesh.jangra@intel.com> wrote:
>
> This patch has the changes to list all supported commands and fix
> supported commands help details.
>
> Fixes: 5074e1d55107 ("examples/pipeline: add configuration commands")
>
> Signed-off-by: Yogesh Jangra <yogesh.jangra@intel.com>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Please, do not forget the version number on the patches you send.
Applied, thanks.
--
David Marchand
prev parent reply other threads:[~2020-10-23 11:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 11:01 Yogesh Jangra
2020-10-23 11:45 ` David Marchand [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=CAJFAV8yS94Dd9hgtNRFDgADCVtqV5sGBCr-yVgyo5RXYg-kLPQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=yogesh.jangra@intel.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).