DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: "Dharmappa, Savinay" <savinay.dharmappa@intel.com>
Cc: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
	 "Singh, Jasvinder" <jasvinder.singh@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	 Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v2] examples/qos_sched: update profile oversubscribe config file
Date: Tue, 17 Nov 2020 08:21:44 +0100	[thread overview]
Message-ID: <CAJFAV8wxc-eyostE+mnSnB70dNjeBB+FzexhrZXKJxVRHUtMig@mail.gmail.com> (raw)
In-Reply-To: <BL0PR11MB3491F9278647FD55580B4E33E8E20@BL0PR11MB3491.namprd11.prod.outlook.com>

On Tue, Nov 17, 2020 at 8:05 AM Dharmappa, Savinay
<savinay.dharmappa@intel.com> wrote:
> If so, please submit one patch fixing the qos_sched example (both config and doc) and another patch for fixing the ip_pipeline (doc).
> In both of them, describe with a Fixes: tag which commits are being fixed.
>
> >>  Instead of new patch shall I send v3 of this patch which has (both config and doc) and similarly for https://patchwork.dpdk.org/patch/81666/  patch to have only ip_pipeline (doc). Please let me know.

Yes, one patch for qos_shed and one patch for ip_pipeline.

-- 
David Marchand


  reply	other threads:[~2020-11-17  7:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 13:41 [dpdk-dev] [PATCH v1] sched: " Savinay Dharmappa
2020-10-27  9:22 ` [dpdk-dev] [PATCH v2] examples/qos_sched: " Savinay Dharmappa
2020-10-27  9:45   ` Dumitrescu, Cristian
2020-11-05  9:39     ` Dharmappa, Savinay
2020-11-05 10:11       ` Thomas Monjalon
2020-11-13 13:58       ` David Marchand
2020-11-17  7:05         ` Dharmappa, Savinay
2020-11-17  7:21           ` David Marchand [this message]
2020-11-17 10:06   ` [dpdk-dev] [PATCH v3] examples/qos_sched: update profile " Savinay Dharmappa
2020-11-20 12:17     ` David Marchand

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=CAJFAV8wxc-eyostE+mnSnB70dNjeBB+FzexhrZXKJxVRHUtMig@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=jasvinder.singh@intel.com \
    --cc=savinay.dharmappa@intel.com \
    --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).