From: Bruce Richardson <bruce.richardson@intel.com>
To: Keith Wiles <keith.wiles@windriver.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] Add external parser support for unknown commands.
Date: Mon, 3 Nov 2014 10:41:30 +0000 [thread overview]
Message-ID: <20141103104129.GA4840@bricha3-MOBL3> (raw)
In-Reply-To: <1414967308-69530-1-git-send-email-keith.wiles@windriver.com>
On Sun, Nov 02, 2014 at 04:28:28PM -0600, Keith Wiles wrote:
> Allow for a external parser to handle the command line if the
> command is not found and the developer has called the routine
> int cmdline_set_external_parser(struct cmdline * cl,
> cmdline_external_parser_t parser);
> function to set the function pointer.
>
> The function for the external parser function should return CMDLINE_PARSE_NOMATCH
> if not able to match the command requested or zero is handled.
>
> Prototype of external routine:
> int (*cmdline_external_parser_t)(struct cmdline * cl, const char * buy);
>
> Signed-off-by: Keith Wiles <keith.wiles@windriver.com>
Hi Keith,
what is the expected use case for this? Is it for embedding other programming languages alongside the existing DPDK command-line or some other purpose? [Perhaps the use case could be called out in the patch description]
/Bruce
next prev parent reply other threads:[~2014-11-03 10:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 22:28 Keith Wiles
2014-11-03 10:41 ` Bruce Richardson [this message]
2014-11-03 14:08 ` Wiles, Roger Keith
2014-11-03 14:16 ` Bruce Richardson
2014-11-03 14:25 ` Wiles, Roger Keith
2014-11-03 16:06 ` Neil Horman
2014-11-03 16:50 ` Wiles, Roger Keith
2014-11-03 23:26 ` Stephen Hemminger
2014-11-03 23:42 ` Neil Horman
2014-11-04 4:52 ` Wiles, Roger Keith
2014-11-04 11:27 ` Neil Horman
2014-11-04 14:44 ` Wiles, Roger Keith
2014-11-04 19:29 ` Neil Horman
2014-11-04 20:45 ` Wiles, Roger Keith
2014-11-05 15:11 ` Neil Horman
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=20141103104129.GA4840@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@windriver.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).