DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: Nikhil Rao <nikhil.rao@intel.com>, dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] eventdev: fix port id argument in Rx adapter caps API
Date: Tue, 25 Sep 2018 14:52:31 +0200	[thread overview]
Message-ID: <1846637.ZT10i6Abfj@xps> (raw)
In-Reply-To: <20180925095626.GA20972@jerin>

25/09/2018 11:56, Jerin Jacob:
> From: Thomas Monjalon <thomas@monjalon.net>
> > 25/09/2018 11:15, Jerin Jacob:
> > > From: Nikhil Rao <nikhil.rao@intel.com>
> > > > @@ -162,7 +164,7 @@ The libraries prepended with a plus sign were incremented in this version.
> > > >       librte_distributor.so.1
> > > >       librte_eal.so.8
> > > >       librte_ethdev.so.10
> > > > -     librte_eventdev.so.4
> > > > +   + librte_eventdev.so.6
> > >
> > > Can you send a separate standalone patch to fixup doc/guides/rel_notes/release_18_08.rst
> > > release notes. The version(change to librte_eventdev.so.5) should have been
> > > updated in change set in 3810ae4357.
> > >
> > > +Thomas,
> > > In case if he has difference in opinion on updating released release note file.
> > 
> > I prefer such changes being atomic.
> 
> Me too. But the offending change set(3810ae4357) is old
> ➜ [master][dpdk.org] $ git describe  3810ae4357
> v18.05-389-g3810ae435

Oh, I had not understood :-)

> Do you prefer to have patch to update the release_18_08.rst file or ignore it?

Yes you can patch release_18_08.rst and release_18_11.rst with a fix
to version librte_eventdev.so.5, and Cc:stable for backport in 18.08.

Thanks

  reply	other threads:[~2018-09-25 12:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-05 12:21 [dpdk-dev] [PATCH 1/2] " Nikhil Rao
2018-09-05 12:21 ` [dpdk-dev] [PATCH 2/2] test/event: change ethernet port ids to be 16 bit Nikhil Rao
2018-09-17 14:14 ` [dpdk-dev] [PATCH 1/2] eventdev: fix port id argument in Rx adapter caps API Jerin Jacob
2018-09-25  8:49 ` [dpdk-dev] [PATCH v2] " Nikhil Rao
2018-09-25  9:15   ` Jerin Jacob
2018-09-25  9:50     ` Thomas Monjalon
2018-09-25  9:56       ` Jerin Jacob
2018-09-25 12:52         ` Thomas Monjalon [this message]
2018-09-25  9:49 ` [dpdk-dev] [PATCH v3] " Nikhil Rao
2018-09-28 14:54   ` Jerin Jacob

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=1846637.ZT10i6Abfj@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.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).