patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dpdk-dev <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>,
	stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v4 1/6] event/dpaa2: fix def queue conf
Date: Mon, 30 Sep 2019 19:47:34 +0530	[thread overview]
Message-ID: <CALBAE1PfMVkCkm+d4+dFpZbZww4t1oHSZ27Y50-8h=ezPUScuw@mail.gmail.com> (raw)
In-Reply-To: <20190930083215.8241-2-hemant.agrawal@nxp.com>

On Mon, Sep 30, 2019 at 2:04 PM Hemant Agrawal <hemant.agrawal@nxp.com> wrote:
>
> Test vector expect only one type of scheduling as default.
> The old code is provide support scheduling types instead of default.
>
> Fixes: 13370a3877a5 ("eventdev: fix inconsistency in queue config")
> Cc: stable@dpdk.org
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>

Series applied to dpdk-next-eventdev/master. Thanks.

      reply	other threads:[~2019-09-30 14:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190906103410.14996-1-hemant.agrawal@nxp.com>
2019-09-06 10:34 ` [dpdk-stable] [PATCH 1/5] " Hemant Agrawal
     [not found] ` <20190907064209.30686-1-hemant.agrawal@nxp.com>
2019-09-07  6:42   ` [dpdk-stable] [PATCH v2 " Hemant Agrawal
2019-09-13  6:24     ` [dpdk-stable] [dpdk-dev] " Jerin Jacob
2019-09-26 17:55       ` Jerin Jacob
2019-09-27  6:02         ` Hemant Agrawal
     [not found]   ` <20190927075841.21841-1-hemant.agrawal@nxp.com>
2019-09-27  7:58     ` [dpdk-stable] [PATCH 1/6] " Hemant Agrawal
2019-09-30  6:43       ` [dpdk-stable] [dpdk-dev] " Jerin Jacob
     [not found]     ` <20190930083215.8241-1-hemant.agrawal@nxp.com>
2019-09-30  8:32       ` [dpdk-stable] [PATCH v4 " Hemant Agrawal
2019-09-30 14:17         ` Jerin Jacob [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='CALBAE1PfMVkCkm+d4+dFpZbZww4t1oHSZ27Y50-8h=ezPUScuw@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerinj@marvell.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).