DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, david.marchand@redhat.com,
	arybchenko@solarflare.com, ferruh.yigit@intel.com,
	bruce.richardson@intel.com, ajit.khaparde@broadcom.com,
	jerinj@marvell.com, maxime.coquelin@redhat.com,
	akhil.goyal@nxp.com, bluca@debian.org, ktraynor@redhat.com,
	honnappa.nagarahalli@arm.com
Subject: Re: [dpdk-dev] [PATCH] usertools: warn about future removal of setup script
Date: Fri, 07 Aug 2020 13:40:41 +0200	[thread overview]
Message-ID: <4228305.L8bQdx333B@thomas> (raw)
In-Reply-To: <20200806111420.25e4ce16@hermes.lan>

06/08/2020 20:14, Stephen Hemminger:
> On Thu,  6 Aug 2020 19:13:03 +0200
> Thomas Monjalon <thomas@monjalon.net> wrote:
> 
> > As agreed in the deprecation notice, the "generic" script
> > to setup the Linux environment will be removed in DPDK 20.11.
> > Some specific parts may be converted into dedicated scripts.
> > 
> > In the meantime, a warning will be printed to users of this script.
> > 
> > Suggested-by: Stephen Hemminger <stephen@networkplumber.org>
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> > ---
> > --- a/usertools/dpdk-setup.sh
> > +++ b/usertools/dpdk-setup.sh
> > @@ -592,6 +592,10 @@ while [ "$QUIT" == "0" ]; do
> >  	echo "[$OPTION_NUM] Exit Script"
> >  	OPTIONS[$OPTION_NUM]="quit"
> >  	echo ""
> > +	echo '--------------------------------------------------'
> > +	echo 'WARNING: This tool will be removed from DPDK 20.11'
> > +	echo '--------------------------------------------------'
> > +	echo
> >  	echo -n "Option: "
> >  	read our_entry
> >  	echo ""
> 
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>

Applied



      reply	other threads:[~2020-08-07 11:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 17:13 Thomas Monjalon
2020-08-06 18:14 ` Stephen Hemminger
2020-08-07 11:40   ` Thomas Monjalon [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=4228305.L8bQdx333B@thomas \
    --to=thomas@monjalon.net \
    --cc=ajit.khaparde@broadcom.com \
    --cc=akhil.goyal@nxp.com \
    --cc=arybchenko@solarflare.com \
    --cc=bluca@debian.org \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=jerinj@marvell.com \
    --cc=ktraynor@redhat.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=stephen@networkplumber.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).