patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Sarosh Arif <sarosh.arif@emumba.com>
Cc: dev@dpdk.org, stable@dpdk.org, m.bilal@emumba.com
Subject: Re: [dpdk-stable] [PATCH v2] usertools/dpdk-setup.sh: fix dpdk-setup's behaviour on non-alphanumeric inputs
Date: Sun, 24 May 2020 19:04:11 +0200	[thread overview]
Message-ID: <2167876.Wqe6pE9kz3@thomas> (raw)
In-Reply-To: <CABoZmYOjxNzu02QdLrmet8Xt3cmXrMHRbbO=M3sA=0m9sVucbw@mail.gmail.com>

Hello,

17/04/2020 14:50, Sarosh Arif:
> Hello,
> If there is no objection on this patch then it can perhaps be applied.

There are 3 issues here:
1/ There is no maintainer for this script (and no review of the patch)
2/ There is no explanation in this patch (probably explaining the lack of review)
3/ There is a more recent patch (not a v3), probably superseding this one:
	https://patches.dpdk.org/patch/67855/



> On Fri, Mar 20, 2020 at 11:50 AM Sarosh Arif <sarosh.arif@emumba.com> wrote:
> 
> > Bugzilla ID: 419
> > Cc: stable@dpdk.org
> > Signed-off-by: Sarosh Arif <sarosh.arif@emumba.com>
> > ---
> >  usertools/dpdk-setup.sh | 14 ++++++++++----
> >  1 file changed, 10 insertions(+), 4 deletions(-)




  reply	other threads:[~2020-05-24 17:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200319174423.28378>
2020-03-20  6:50 ` Sarosh Arif
2020-04-17 12:50   ` Sarosh Arif
2020-05-24 17:04     ` Thomas Monjalon [this message]
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         ` [dpdk-stable] [dpdk-dev] " Stephen Hemminger
2020-07-24 13:29           ` 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=2167876.Wqe6pE9kz3@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=m.bilal@emumba.com \
    --cc=sarosh.arif@emumba.com \
    --cc=stable@dpdk.org \
    /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).