Re: [dpdk-stable] please help backporting some patches to LTS release 17.11.1

["Burakov, Anatoly" <anatoly.burakov@intel.com>]

Hi all,

It seems that this patch has never made it into 17.11 stable. Is there anything that I can do to make it happen?

Thanks,
Anatoly

> -----Original Message-----
> From: Burakov, Anatoly
> Sent: Tuesday, February 20, 2018 11:03 AM
> To: 'Yuanhan Liu' <yliu@fridaylinux.org>
> Cc: 'dpdk stable' <stable@dpdk.org>
> Subject: RE: please help backporting some patches to LTS release 17.11.1
> 
> Hi,
> 
> The commit in question will apply, if previous changes are applied,
> specifically, patch fixing a typo [1]. After these patches are applied
> (specifically, the first one), the patch in question [2] should apply as well.
> 
> [1] http://dpdk.org/dev/patchwork/patch/32587/
> [2] http://dpdk.org/dev/patchwork/patch/34813/
> 
> Thanks,
> Anatoly
> 
> > -----Original Message-----
> > From: Burakov, Anatoly
> > Sent: Tuesday, February 13, 2018 11:49 AM
> > To: Yuanhan Liu <yliu@fridaylinux.org>
> > Cc: dpdk stable <stable@dpdk.org>
> > Subject: RE: please help backporting some patches to LTS release
> > 17.11.1
> >
> > I must've checked out the wrong branch then. I'll double-check. My
> > apologies!
> >
> > Thanks,
> > Anatoly
> >
> >
> > > -----Original Message-----
> > > From: Yuanhan Liu [mailto:yliu@fridaylinux.org]
> > > Sent: Tuesday, February 13, 2018 11:47 AM
> > > To: Burakov, Anatoly <anatoly.burakov@intel.com>
> > > Cc: dpdk stable <stable@dpdk.org>
> > > Subject: Re: please help backporting some patches to LTS release
> > > 17.11.1
> > >
> > > On Mon, Feb 12, 2018 at 10:36:23AM +0000, Burakov, Anatoly wrote:
> > > > Hi,
> > > >
> > > > I've looked at commit 5c45e0f. This patch cannot be backported
> > > > before
> > > 71330483 [1] is applied, as it depends on changes made in that patch.
> > > >
> > > > http://dpdk.org/dev/patchwork/patch/31276/
> > > >
> > > > Logs show that it was CC'd to stable, but it looks like it wasn't
> > > > integrated
> > > into stable.
> > >
> > > That patch is part of the v17.11 release (was merged after v17.11-rc3).
> > > So it's also in the 17.11 stable branch.
> > >
> > > 	--yliu
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Yuanhan Liu [mailto:yliu@fridaylinux.org]
> > > > > Sent: Wednesday, February 7, 2018 9:32 AM
> > > > > To: dpdk stable <stable@dpdk.org>
> > > > > Cc: Burakov, Anatoly <anatoly.burakov@intel.com>; Xing, Beilei
> > > > > <beilei.xing@intel.com>; Iremonger, Bernard
> > > > > <bernard.iremonger@intel.com>; Harish Patil
> > > > > <harish.patil@cavium.com>; Nelio Laranjeiro
> > > > > <nelio.laranjeiro@6wind.com>; Olivier Matz
> > > > > <olivier.matz@6wind.com>; Ophir Munk <ophirmu@mellanox.com>;
> > Pavan
> > > > > Nikhilesh <pbhagavatula@caviumnetworks.com>; Zhang, Qi Z
> > > > > <qi.z.zhang@intel.com>; Shahaf Shuler <shahafs@mellanox.com>;
> > > > > Varghese, Vipin <vipin.varghese@intel.com>; Yongseok Koh
> > > > > <yskoh@mellanox.com>; Yong Wang <wang.yong19@zte.com.cn>
> > > > > Subject: please help backporting some patches to LTS release
> > > > > 17.11.1
> > > > >
> > > > > Hi commit authors (and maintainers),
> > > > >
> > > > > I didn't manage to apply following commits from upstream to
> > > > > stable branch
> > > > > 17.11: conflict happens. I'm wondering can the authors check the
> > > > > following list and backport those patches belong to you?
> > > > >
> > > > > FYI, branch 17.11 is located at tree:
> > > > >    git://dpdk.org/dpdk-stable
> > > > >
> > > > > It'd be great if you could do that in one weeks. Also, please
> > > > > add a heading line like below before the commit log body:
> > > > >     [ backported from upstream commit xxx ]
> > > > >
> > > > > Example: http://dpdk.org/browse/dpdk-
> > > > >
> > >
> stable/commit/?h=16.07&id=c4831394c7d1944d8ec27d52c22997f20d19718e
> > > > >
> > > > > Please let me know if you have any comments, say, need more
> > > > > time, or it's worthless to packport it. And please send it to
> > > > > "stable@dpdk.org", but not "dev@dpdk.org".
> > > > >
> > > > > Also, please make an reply to me when you have done that, just
> > > > > in case I may miss the backport email.
> > > > >
> > > > > Thanks.
> > > > >
> > > > > 	-yliu
> > > > >
> > > > > ---
> > > > > 5c45e0f  Anatoly Burakov  test/memzone: handle previously
> > > > > allocated memzones
> > > > > 4ab8314  Beilei Xing      net/i40e: fix interrupt conflict with multi-driver
> > > > > cfdfca4  Beilei Xing      net/i40e: fix multiple driver support
> > > > > 378cc7f  Beilei Xing      net/i40e: fix Rx interrupt
> > > > > 5cbf8b4  Bernard Iremonger test/flow_classify: remove port bound
> > > > > requirement
> > > > > dd28bc8  Harish Patil     net/qede: fix VF port creation sequence
> > > > > c3299d7  Nélio Laranjeiro net/mlx5: fix flow priority on queue
> > > > > action f07f9bc Nélio Laranjeiro net/mlx5: fix port stop by
> > > > > verify flows are still present
> > > > > 51e7fa8  Nélio Laranjeiro net/mlx5: fix secondary process verification
> > > > > 35906ac  Olivier Matz     net/bnxt: fix headroom initialization
> > > > > 70205b5  Ophir Munk       net/failsafe: fix default Tx offloads
> capabilities
> > > > > 452cd79  Pavan Nikhilesh  app/eventdev: fix event device queue
> count
> > > > > dd18b06  Qi Zhang         net/e1000: fix mailbox interrupt handler
> > > > > 6810c63  Qi Zhang         net/ixgbe: fix mailbox interrupt handler
> > > > > cd230a3  Shahaf Shuler    net/mlx5: fix CRC strip capability query
> > > > > e313ef4  Shahaf Shuler    net/mlx5: fix link state on device start
> > > > > da23f0a  Vipin Varghese   service: fix memory leak with new function
> > > > > c7bf622  Yongseok Koh     net/mlx5: fix handling link status event
> > > > > 0ff7683  Yong Wang        net/dpaa: fix potential memory leak