From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
Cc: dpdk stable <stable@dpdk.org>,
Adrien Mazarguil <adrien.mazarguil@6wind.com>
Subject: Re: [dpdk-stable] please help backporting some patches to stable release 16.11.1
Date: Mon, 20 Feb 2017 16:06:28 +0800 [thread overview]
Message-ID: <20170220080628.GB18844@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <20170217131530.GQ23344@autoinstall.dev.6wind.com>
On Fri, Feb 17, 2017 at 02:15:30PM +0100, Nélio Laranjeiro wrote:
> On Wed, Feb 15, 2017 at 02:38:50PM +0800, Yuanhan Liu wrote:
> > Hi commit authors (and maintainers),
> >
> > I tried to pick following commits from upstream to stable branch 16.11,
> > but I failed: they can't be applied. I'm wondering can the authors check
> > the following list and backport some patches belong to them?
> >
> > FYI, branch 16.11 at git://dpdk.org/dpdk-stable is the place those patches
> > should be packported to. It'd be great if you could do that in one week. If
> > so, please do me a favor by adding a heading line like following 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".
> >
> > If you don't have time recently, you could backport them later, then they
> > will be candidates for 16.11.2.
> >
> > Thanks.
> >
> > -yliu
> >
> > ---
> > 9b66721 Qi Zhang net/ixgbe: fix blocked interrupts
> > 0603df7 Nélio Laranjeiro net/mlx5: fix Rx packet validation and type
> > a9f2fbc Shahaf Shuler net/mlx5: fix inconsistent link status
> > f04f1d5 Nélio Laranjeiro net/mlx5: fix Tx WQE corruption caused by starvation
> > 8fcd6c2 Nélio Laranjeiro net/mlx5: fix inline WQE consumption
> > 76bf157 Yongseok Koh net/mlx5: fix updating total length of multi-packet send
> > 3a49ffe Shahaf Shuler net/mlx5: fix link status query
>
> Yuanhan,
>
> - 0603df7 Nélio Laranjeiro net/mlx5: fix Rx packet validation and type
>
> Depends on another fix:
> 501505c5608a "net/mlx: fix IPv4 and IPv6 packet type",
> please apply this one before and mine will then apply without any
> conflict.
Thanks!
This one is actually applied. It turned out to be another issue of
"git am fails while git cherry-pick works", as stated in following
reply:
http://dpdk.org/ml/archives/stable/2017-February/001044.html
I will update my script and now it's applied.
For the same reason, 76bf157 ("net/mlx5: fix updating total length
of multi-packet send") is also applied.
> According to our discussion [1], please do not handle the following
> patches:
>
> - f04f1d5 Nélio Laranjeiro net/mlx5: fix Tx WQE corruption caused by starvation
> - 8fcd6c2 Nélio Laranjeiro net/mlx5: fix inline WQE consumption
>
> They need to be totally re-written to apply on top of DPDK 16.11 stable
> branch.
Okay, thanks for the note!
Now, there is only one left: a9f2fbc ("net/mlx5: fix inconsistent link
status"). Woud you or Shahaf (the author) backport it, please?
I plan to do a stable patches review today or tomorrow, then the final
release will be out in about 2 weeks. If you could do that before it,
that'd be great. If not, it will be postponed to next release.
--yliu
>
> Thanks,
>
> [1] http://dpdk.org/ml/archives/stable/2017-February/001041.html
>
> --
> Nélio Laranjeiro
> 6WIND
next prev parent reply other threads:[~2017-02-20 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 6:38 Yuanhan Liu
2017-02-17 13:15 ` Nélio Laranjeiro
2017-02-20 8:06 ` Yuanhan Liu [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-23 10:52 Yuanhan Liu
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=20170220080628.GB18844@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=nelio.laranjeiro@6wind.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).