All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Dharmappa, Savinay" <savinay.dharmappa@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Singh, Jasvinder" <jasvinder.singh@intel.com>,
	"Shetty, Praveen" <praveen.shetty@intel.com>,
	"Tummala, Sivaprasad" <sivaprasad.tummala@intel.com>,
	"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
	"Pai G, Sunil" <sunil.pai.g@intel.com>
Subject: Re: [dpdk-dev] [PATCH v4] doc: add deprecation notice for sched changes
Date: Sat, 08 Aug 2020 00:49:06 +0200	[thread overview]
Message-ID: <13768028.YTmxOK8GxI@thomas> (raw)
In-Reply-To: <4775075.J1WSsk4pCz@thomas>

06/08/2020 16:16, Thomas Monjalon:
> > > Add deprecation note for making changes in data structures and APIs in order to
> > > allow dynamic configuration of subport bandwidth profile.
> > > These changes are aligned as suggested in the RFC[1].
> > > 
> > > https://mails.dpdk.org/archives/dev/2020-July/175161.html
> > > 
> > > Signed-off-by: Savinay Dharmappa <savinay.dharmappa@intel.com>
> > > Acked-by: Jasvinder Singh <jasvinder.singh@intel.com>
> > > Acked-by: Praveen Shetty <praveen.shetty@intel.com>
> > Acked-by: Sunil Pai G <sunil.pai.g@intel.com>
> 
> It seems all acks are from the same team.
> Any other opinion?

Applied



      reply	other threads:[~2020-08-07 22:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 10:28 [dpdk-dev] [PATCH] doc: add deprecation notice for sched changes Savinay Dharmappa
2020-07-16 13:25 ` [dpdk-dev] [PATCH v2] " Savinay Dharmappa
2020-07-27 11:16   ` Shetty, Praveen
2020-07-29  5:13   ` [dpdk-dev] [PATCH v3] " Savinay Dharmappa
2020-07-29 11:08     ` [dpdk-dev] [PATCH v4] " Savinay Dharmappa
2020-08-04 14:14       ` Pai G, Sunil
2020-08-06 14:16         ` Thomas Monjalon
2020-08-07 22:49           ` 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=13768028.YTmxOK8GxI@thomas \
    --to=thomas@monjalon.net \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=jasvinder.singh@intel.com \
    --cc=praveen.shetty@intel.com \
    --cc=savinay.dharmappa@intel.com \
    --cc=sivaprasad.tummala@intel.com \
    --cc=sunil.pai.g@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.