From: Stephen Hemminger <stephen@networkplumber.org>
To: Sarosh Arif <sarosh.arif@emumba.com>
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
Muhammad Bilal <m.bilal@emumba.com>,
stable@dpdk.org, "Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v4] usertools/dpdk-setup.sh: fix dpdk-setup's behaviour on non-alphanumeric inputs
Date: Thu, 23 Jul 2020 10:00:05 -0700 [thread overview]
Message-ID: <20200723100005.670088e1@hermes.lan> (raw)
In-Reply-To: <CABoZmYO0+cxHXKuQrkgx2bgdGZ30RT2zgP52fBVOeW84mHg3dg@mail.gmail.com>
On Thu, 23 Jul 2020 17:13:17 +0500
Sarosh Arif <sarosh.arif@emumba.com> wrote:
> Since this script has no maintainer who is responsible for providing ACK or
> NAK on the patches related to this script?
>
> On Tue, Jun 2, 2020 at 12:39 PM Sarosh Arif <sarosh.arif@emumba.com> wrote:
>
> > Combine https://patches.dpdk.org/patch/67855/ with v2 of this patch to fix
> > the overall behaviour of dpdk-setup.sh on non-alphanumeric inputs.
> > Instead of crashing the script will prompt the user to re-enter the input
> > in case of non-alphanumeric input.
> >
> > Bugzilla ID: 419
> > Signed-off-by: Sarosh Arif <sarosh.arif@emumba.com>
> > Signed-off-by: Muhammad Bilal <m.bilal@emumba.com>
If no maintainer is defined for a subtree, it should be responsiblity
of the core maintainers to handle it.
PS: dpdk-setup has out grown its welcome, and a better version with
a real UI is needed.
next prev parent reply other threads:[~2020-07-23 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200319174423.28378>
2020-03-20 6:50 ` [dpdk-stable] [PATCH v2] " Sarosh Arif
2020-04-17 12:50 ` Sarosh Arif
2020-05-24 17:04 ` Thomas Monjalon
2020-06-01 8:40 ` [dpdk-stable] [PATCH v3] " Sarosh Arif
2020-06-02 7:38 ` [dpdk-stable] [PATCH v4] " Sarosh Arif
2020-07-23 12:13 ` Sarosh Arif
2020-07-23 17:00 ` Stephen Hemminger [this message]
2020-07-24 13:29 ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
2020-07-24 14:05 ` Jerin Jacob
2020-11-26 17:54 ` Thomas Monjalon
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=20200723100005.670088e1@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=m.bilal@emumba.com \
--cc=sarosh.arif@emumba.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).