patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Yongseok Koh <yskoh@mellanox.com>
Cc: Yuanhan Liu <yliu@fridaylinux.org>, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to LTS	release 17.11.1
Date: Thu, 7 Mar 2019 12:04:42 +0000	[thread overview]
Message-ID: <C6ECDF3AB251BE4894318F4E4512369782EEC0EC@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <FF061693-B674-47F1-805F-8E69D7BAEB22@mellanox.com>

Hi Yongseok,

The patch that's missing is this one:

5c45e0fdeddfc773fab63e12d086c4f2052cda40
[http://patches.dpdk.org/patch/34813/]

However, the patch in question depends on another commit, so that one should be pulled in too:

8ceee8e7dea1fb07f9ccf6a037d0571fea328afc
[http://patches.dpdk.org/patch/32587/]

Thanks,
Anatoly


> -----Original Message-----
> From: Yongseok Koh [mailto:yskoh@mellanox.com]
> Sent: Wednesday, March 6, 2019 7:03 PM
> To: Burakov, Anatoly <anatoly.burakov@intel.com>
> Cc: Yuanhan Liu <yliu@fridaylinux.org>; dpdk stable <stable@dpdk.org>
> Subject: Re: [dpdk-stable] please help backporting some patches to LTS
> release 17.11.1
> 
> Hi, Anatoly
> 
> Please give the list of missing patches of the master branch so that I can
> cherry-pick it for v17.11.6.
> 
> If you don't think those are not cleanly applicable to stable/17.11, you could
> send back-ports to stable@dpdk.org along with the prefix,
> 	git send-email --subject-prefix='PATCH 17.11' ...
> 
> 
> Thanks,
> Yongseok
> 
> > On Mar 6, 2019, at 2:56 AM, Burakov, Anatoly
> <anatoly.burakov@intel.com> wrote:
> >
> > 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]
> >>
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpd
> >>
> k.org%2Fdev%2Fpatchwork%2Fpatch%2F32587%2F&amp;data=02%7C01%7C
> yskoh%4
> >>
> 0mellanox.com%7Ce5ca9a99dae0486a15f608d6a2226f12%7Ca652971c7d2e4d
> 9ba6
> >>
> a4d149256f461b%7C0%7C0%7C636874666108260958&amp;sdata=sX%2FdJSY
> 2U7pIb
> >> tCbKkd5hS%2Fb4XoTrup%2BmIa37qL77wA%3D&amp;reserved=0
> >> [2]
> >>
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpd
> >>
> k.org%2Fdev%2Fpatchwork%2Fpatch%2F34813%2F&amp;data=02%7C01%7C
> yskoh%4
> >>
> 0mellanox.com%7Ce5ca9a99dae0486a15f608d6a2226f12%7Ca652971c7d2e4d
> 9ba6
> >>
> a4d149256f461b%7C0%7C0%7C636874666108260958&amp;sdata=TzsDQFGYy
> wsQDbE
> >> kErfoIz82NksLJbbvc9XLN5e44F4%3D&amp;reserved=0
> >>
> >> 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.
> >>>>>
> >>>>>
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2F
> >>>>>
> dpdk.org%2Fdev%2Fpatchwork%2Fpatch%2F31276%2F&amp;data=02%7C01
> %7Cy
> >>>>>
> skoh%40mellanox.com%7Ce5ca9a99dae0486a15f608d6a2226f12%7Ca652971c
> 7
> >>>>>
> d2e4d9ba6a4d149256f461b%7C0%7C0%7C636874666108260958&amp;sdata=
> H7%
> >>>>> 2BxeaclAJNz3XI4g69JfE9f2R19t844aaohtfW3gpk%3D&amp;reserved=0
> >>>>>
> >>>>> 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:
> >>>>>>
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2
> >>>>>> Fdpdk.org%2Fbrowse%2Fdpdk-
> &amp;data=02%7C01%7Cyskoh%40mellanox.co
> >>>>>>
> m%7Ce5ca9a99dae0486a15f608d6a2226f12%7Ca652971c7d2e4d9ba6a4d1492
> 5
> >>>>>>
> 6f461b%7C0%7C0%7C636874666108260958&amp;sdata=Q7o6uCxSpimpYYujg
> 7%
> >>>>>> 2BLKJf40dIz3Io3Ib%2F%2FRZJvbeI%3D&amp;reserved=0
> >>>>>>
> >>>>
> >>
> 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


  reply	other threads:[~2019-03-07 12:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07  9:31 Yuanhan Liu
2018-02-08  7:44 ` [dpdk-stable] 答复: " wang.yong19
2018-02-08  8:46 ` [dpdk-stable] " Pavan Nikhilesh
2018-02-08  8:56   ` Yuanhan Liu
2018-02-11  4:54 ` Yuanhan Liu
2018-02-12 10:36 ` Burakov, Anatoly
2018-02-13 11:46   ` Yuanhan Liu
2018-02-13 11:49     ` Burakov, Anatoly
2018-02-20 11:02       ` Burakov, Anatoly
2019-03-06 10:56         ` Burakov, Anatoly
2019-03-06 19:03           ` Yongseok Koh
2019-03-07 12:04             ` Burakov, Anatoly [this message]
2019-03-07 20:10               ` Yongseok Koh
2018-02-14  8:58 ` [dpdk-stable] [PATCH 1/3] net/mlx5: fix secondary process verification Nelio Laranjeiro
2018-02-16 13:01   ` Yuanhan Liu
2018-02-14  8:58 ` [dpdk-stable] [PATCH 2/3] net/mlx5: fix port stop by verify flows are still present Nelio Laranjeiro
2018-02-14  8:58 ` [dpdk-stable] [PATCH 3/3] net/mlx5: fix flow priority on queue action Nelio Laranjeiro
2018-02-27  9:36 ` [dpdk-stable] [PATCH 1/3] Revert "net/mlx5: fix flow priority on queue action" Nelio Laranjeiro
2018-02-27  9:49   ` Yuanhan Liu
2018-02-27  9:36 ` [dpdk-stable] [PATCH 2/3] net/mlx5: remove parser/flow drop queue Nelio Laranjeiro
2018-02-27  9:36 ` [dpdk-stable] [PATCH 3/3] net/mlx5: fix flow priority on queue action Nelio Laranjeiro

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=C6ECDF3AB251BE4894318F4E4512369782EEC0EC@IRSMSX107.ger.corp.intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=stable@dpdk.org \
    --cc=yliu@fridaylinux.org \
    --cc=yskoh@mellanox.com \
    /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).