DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andrew Rybchenko <arybchenko@solarflare.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
	Nikhil Rao <nikhil.rao@intel.com>,
	"Erik Gabriel Carrillo" <erik.g.carrillo@intel.com>,
	dev <dev@dpdk.org>,
	"Dilshod Urazov" <Dilshod.Urazov@oktetlabs.ru>,
	dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH 1/3] eventdev: fix to set positive rte_errno
Date: Thu, 4 Jul 2019 14:56:04 +0300	[thread overview]
Message-ID: <2cc5f0f7-f72a-b482-335e-a85ed8ca9ac3@solarflare.com> (raw)
In-Reply-To: <CAJFAV8ztp86sGANMd3e3mqBpfy0jPNjv5FdqOY4MTneCm7y=2A@mail.gmail.com>

On 04.07.2019 14:34, David Marchand wrote:
>
> We have fixes for different releases, expect the stable maintainers to 
> ask for help :-)
>
>
> On Thu, Jul 4, 2019 at 12:04 PM Andrew Rybchenko 
> <arybchenko@solarflare.com <mailto:arybchenko@solarflare.com>> wrote:
>
>     From: Dilshod Urazov <Dilshod.Urazov@oktetlabs.ru
>     <mailto:Dilshod.Urazov@oktetlabs.ru>>
>
>     Fixes: c9bf83947e2e ("eventdev: add eth Tx adapter APIs")
>
>
> v18.11-rc1~724
>
>     Fixes: 47d05b292820 ("eventdev: add timer adapter common code")
>
>
> v18.05-rc1~462
>
>     Fixes: 6750b21bd6af ("eventdev: add default software timer adapter")
>
>
> v18.05-rc1~460
>
>     Fixes: c75f7897ea35 ("eventdev: set error code in port link/unlink
>     functions")
>
>
> v18.02-rc1~202
>
>     Fixes: 7d1acc9dde93 ("eventdev: introduce helper function for
>     enqueue burst")
>
>
> v17.08-rc1~90
>
>     Fixes: 406aed4e0dd9 ("eventdev: add errno-style return values")
>
>
> v17.05-rc1~166
>
>     Fixes: c64e1b7b20d2 ("eventdev: add new software event timer adapter")
>
>
> This last sha1 c64e1b7b20d2 is unknown to my git.
> Please, can you double check?

The patch is for dpdk-next-eventdev tree and this changeset was ther
(but not in main dpdk repo yet).


>
>     Cc: stable@dpdk.org <mailto:stable@dpdk.org>
>
>     Signed-off-by: Dilshod Urazov <Dilshod.Urazov@oktetlabs.ru
>     <mailto:Dilshod.Urazov@oktetlabs.ru>>
>     Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com
>     <mailto:arybchenko@solarflare.com>>
>

[...]

>
> Reviewed-by: David Marchand <david.marchand@redhat.com 
> <mailto:david.marchand@redhat.com>>

Many thanks for review.



  reply	other threads:[~2019-07-04 11:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04 10:03 [dpdk-dev] [PATCH 0/3] eventdev fixes " Andrew Rybchenko
2019-07-04 10:03 ` [dpdk-dev] [PATCH 1/3] eventdev: fix " Andrew Rybchenko
2019-07-04 11:34   ` [dpdk-dev] [dpdk-stable] " David Marchand
2019-07-04 11:56     ` Andrew Rybchenko [this message]
2019-07-04 11:58       ` David Marchand
2019-07-04 12:13         ` [dpdk-dev] [EXT] " Jerin Jacob Kollanukkaran
2019-07-04 10:03 ` [dpdk-dev] [PATCH 2/3] event/sw: " Andrew Rybchenko
2019-07-04 10:43   ` Van Haaren, Harry
2019-07-04 10:03 ` [dpdk-dev] [PATCH 3/3] event/opdl: " Andrew Rybchenko
2019-07-04 11:41   ` 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=2cc5f0f7-f72a-b482-335e-a85ed8ca9ac3@solarflare.com \
    --to=arybchenko@solarflare.com \
    --cc=Dilshod.Urazov@oktetlabs.ru \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=erik.g.carrillo@intel.com \
    --cc=jerinj@marvell.com \
    --cc=nikhil.rao@intel.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).