From: dwilder <dwilder@us.ibm.com>
To: Yongseok Koh <yskoh@mellanox.com>
Cc: dpdk stable <stable@dpdk.org>, Akhil Goyal <akhil.goyal@nxp.com>,
Anoob Joseph <anoob.joseph@caviumnetworks.com>,
Archana Muniganti <muniganti.archana@caviumnetworks.com>,
Chao Zhu <chaozhu@linux.vnet.ibm.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Geoffrey Lv <geoffrey.lv@gmail.com>,
Ilya Maximets <i.maximets@samsung.com>,
Jasvinder Singh <jasvinder.singh@intel.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
Junxiao Shi <git@mail1.yoursunny.com>,
Keith Wiles <keith.wiles@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Nikhil Rao <nikhil.rao@intel.com>,
Pradeep Satyanarayana <pradeep@us.ibm.com>,
Qi Zhang <qi.z.zhang@intel.com>,
Rasesh Mody <rasesh.mody@cavium.com>,
Raslan Darawsheh <rasland@mellanox.com>,
Rosen Xu <rosen.xu@intel.com>,
Sachin Saxena <sachin.saxena@nxp.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Thomas Monjalon <thomas@monjalon.net>,
Tiwei Bie <tiwei.bie@intel.com>
Subject: Re: [dpdk-stable] please help backporting some patches to LTS release 17.11.5
Date: Wed, 16 Jan 2019 16:13:20 -0800 [thread overview]
Message-ID: <a594920c94d0844fbf8179c0873e0683@linux.vnet.ibm.com> (raw)
In-Reply-To: <20190111104355.21617-1-yskoh@mellanox.com>
On 2019-01-11 02:43, Yongseok Koh wrote:
> Hi commit authors (and maintainers),
>
> For some reason, there are 36 missing patches from upstream (up to
> 18.11). I
> could apply 19 patches but I could not apply following patches from
> upstream to
> stable/17.11. Can you please check the following list and backport
> those
<....>
> 6b062d56b David Wilder mem: fix anonymous mapping on Power9
This patch will not be back-ported to 17.11. Our current stance is that
Power9 is not supported on 17.11.
Thanks
next prev parent reply other threads:[~2019-01-17 0:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 10:43 Yongseok Koh
2019-01-11 11:49 ` yoursunny
2019-01-11 22:43 ` Yongseok Koh
2019-01-12 11:46 ` Anoob Joseph
2019-01-15 8:31 ` Akhil Goyal
2019-01-15 16:42 ` Yongseok Koh
[not found] ` <54CBAA185211B4429112C315DA58FF6D3369EBA7@IRSMSX103.ger.corp.intel.com>
2019-01-14 19:37 ` Yongseok Koh
2019-01-17 0:13 ` dwilder [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-29 23:43 Yongseok Koh
2018-11-30 1:40 ` yoursunny
2018-11-30 8:01 ` Yongseok Koh
2018-12-01 0:32 ` dwilder
2018-12-05 19:02 ` Yongseok Koh
2018-12-14 4:34 ` Cao, Yahui
2018-12-14 7:55 ` Yongseok Koh
2018-12-18 8:36 ` Cao, Yahui
2018-12-19 20:00 ` Yongseok Koh
[not found] ` <BYAPR18MB28389793C29112B573D875ADB5840@BYAPR18MB2838.namprd18.prod.outlook.com>
2019-01-11 9:55 ` Yongseok Koh
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=a594920c94d0844fbf8179c0873e0683@linux.vnet.ibm.com \
--to=dwilder@us.ibm.com \
--cc=akhil.goyal@nxp.com \
--cc=anoob.joseph@caviumnetworks.com \
--cc=chaozhu@linux.vnet.ibm.com \
--cc=ferruh.yigit@intel.com \
--cc=geoffrey.lv@gmail.com \
--cc=git@mail1.yoursunny.com \
--cc=i.maximets@samsung.com \
--cc=jasvinder.singh@intel.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=keith.wiles@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=muniganti.archana@caviumnetworks.com \
--cc=nikhil.rao@intel.com \
--cc=pradeep@us.ibm.com \
--cc=qi.z.zhang@intel.com \
--cc=rasesh.mody@cavium.com \
--cc=rasland@mellanox.com \
--cc=rosen.xu@intel.com \
--cc=sachin.saxena@nxp.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--cc=tiwei.bie@intel.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).