patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Yuanhan Liu <yliu@fridaylinux.org>
To: Shahaf Shuler <shahafs@mellanox.com>
Cc: Yongseok Koh <yskoh@mellanox.com>,
	"luca.boccassi@gmail.com" <luca.boccassi@gmail.com>,
	Wisam Monther <wisamm@mellanox.com>,
	dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] A missing mlx5 patch for stable 17.11
Date: Sat, 2 Jun 2018 13:14:59 +0800	[thread overview]
Message-ID: <20180602051459.qxz227jwgee2tndm@yuanhanliu-NB0.tencent.com> (raw)
In-Reply-To: <DB7PR05MB4426792F9BD28AF1002C0199C36D0@DB7PR05MB4426.eurprd05.prod.outlook.com>

On Tue, May 29, 2018 at 06:51:14AM +0000, Shahaf Shuler wrote:
> Hi Yuanhan,
> 
> Sunday, May 27, 2018 6:16 AM, Yuanhan Liu:
> > Subject: Re: A missing mlx5 patch for stable 17.11
> > 
> > On Wed, May 23, 2018 at 09:07:56PM +0000, Yongseok Koh wrote:
> > > Hi, Yuanhan
> > >
> > > There's one missing patch from upstream repo. It is because the patch
> > > doesn't have Cc tag. I should've asked when I acked it.
> > >
> > > Please push this one to the 17.11 queue for the next available release.
> > > I confirmed it can be applied without any conflict.
> > 
> > Hi Yongseok,
> > 
> > Thank you for letting me know that! I have now pushed it to dpdk-
> > stable/17.11.
> 
> In fact there is a bunch of fixes that we plan to backport to 17.11. they are currently missing probably to rebase issues.
> We will send them out by EOW. 

Thank you! And please make sure they are well tested.

	--yliu

      reply	other threads:[~2018-06-02  5:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-23 21:07 Yongseok Koh
2018-05-27  3:15 ` Yuanhan Liu
2018-05-29  6:51   ` Shahaf Shuler
2018-06-02  5:14     ` Yuanhan Liu [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=20180602051459.qxz227jwgee2tndm@yuanhanliu-NB0.tencent.com \
    --to=yliu@fridaylinux.org \
    --cc=luca.boccassi@gmail.com \
    --cc=shahafs@mellanox.com \
    --cc=stable@dpdk.org \
    --cc=wisamm@mellanox.com \
    --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).