From: Yongseok Koh <yskoh@mellanox.com>
To: Akhil Goyal <akhil.goyal@nxp.com>
Cc: Anoob Joseph <anoobj@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Narayana Prasad Raju Athreya <pathreya@marvell.com>,
Archana Muniganti <marchana@marvell.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to LTS release 17.11.5
Date: Tue, 15 Jan 2019 16:42:37 +0000 [thread overview]
Message-ID: <EBB56169-F642-4CC1-8E80-EA9ADC1050C1@mellanox.com> (raw)
In-Reply-To: <VI1PR04MB4893C568294EBEAB235BF5D8E6810@VI1PR04MB4893.eurprd04.prod.outlook.com>
Okay, thanks.
Will remove "examples/ipsec-secgw: fix wrong session size" from the list.
Yongseok
> On Jan 15, 2019, at 12:31 AM, Akhil Goyal <akhil.goyal@nxp.com> wrote:
>
> Hi Anoob,
>
> Yes, the API rte_security_session_get_size() is not part of 17.11, hence the patch should not be backported.
>
> -Akhil
>
> -----Original Message-----
> From: Anoob Joseph [mailto:anoobj@marvell.com]
> Sent: Saturday, January 12, 2019 5:17 PM
> To: Akhil Goyal <akhil.goyal@nxp.com>
> Cc: Yongseok Koh <yskoh@mellanox.com>; Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Narayana Prasad Raju Athreya <pathreya@marvell.com>; Archana Muniganti <marchana@marvell.com>; stable@dpdk.org
> Subject: RE: please help backporting some patches to LTS release 17.11.5
>
> Hi Akhil,
>
> This is in reference to backporting the commit,
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.dpdk.org%2Fnext%2Fdpdk-next-crypto%2Fcommit%2F%3Fid%3D2e960c97c6b9311bea90b775e21a4b99ac1d50dc&data=02%7C01%7Cyskoh%40mellanox.com%7C69c9aad602c84ae8cbc708d67ac3d806%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636831378898330412&sdata=YdEy5jzMulwYtcmJ41UMawmA%2FoicJL6ZSsA%2FERfOmZg%3D&reserved=0
>
> It seems like the API used for getting security session size(rte_security_session_get_size()) is not part of 17.11 stable release. Can you advise on how to proceed?
>
> Thanks,
> Anoob
>
>> -----Original Message-----
>> From: Yongseok Koh <yskoh@mellanox.com>
>> Sent: 11 January 2019 16:14
>> To: dpdk stable <stable@dpdk.org>
>> Cc: 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>; David Wilder <dwilder@us.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: please help backporting some patches to LTS release 17.11.5
>>
>> 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 patches?
>>
>> FYI, branch 17.11 is located at tree:
>> git://dpdk.org/dpdk-stable
>>
>> It'd be great if you could do that in one week as I will release RC2
>> soon. Also, please add a line like below before the commit log body:
>> [ backported from upstream commit xxx ]
>>
>> Example:
>> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpdk
>> .org%2Fbrowse%2Fdpdk-&data=02%7C01%7Cakhil.goyal%40nxp.com%7C04d41
>> a446c79484b4d3c08d67883aa5b%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0
>> %7C636828904248639074&sdata=6xaFuk01YSfUHC%2Bb9e7OxdivzuOZnyNDyFUt
>> TLuqDZY%3D&reserved=0
>> stable/commit/?h=16.07&id=c4831394c7d1944d8ec27d52c22997f20d19718e
>>
>> Also please mention the target LTS in the subject line, as we have
>> more than one at the same time, for example:
>>
>> [PATCH 17.11] foo/bar: fix baz
>>
>> With git send-email, this can be achieved by appending the parameter:
>>
>> --subject-prefix='17.11'
>>
>> 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".
>>
>> Thanks,
>> Yongseok
>>
>> ---
>> 2e960c97c Anoob Joseph examples/ipsec-secgw: fix wrong session size
>> 6b062d56b David Wilder mem: fix anonymous mapping on Power9
>> 66cdfd67c Jasvinder Singh net/softnic: fix undefined device info fields
>> 13ffe6059 Jerin Jacob doc: clarify VLAN and QinQ Tx offload prerequisite
>> f49d7e9a9 Junxiao Shi cryptodev: fix pool element size for undefined
>> operation
>> 74ee315e4 Maxime Coquelin vhost: fix error handling when mem table
>> gets updated
>> d7b5f102c Nikhil Rao eventdev: fix eth Rx adapter hotplug incompatibility
>> 475425186 Nikhil Rao eventdev: fix port id argument in Rx adapter caps
>> e846cfdec Nikhil Rao eventdev: fix unlock in Rx adapter
>> 55e411b30 Qi Zhang bus/pci: fix resource mapping override
>> d5df6159d Rasesh Mody net/qede: fix ethernet type in HW registers
>> 9396ad334 Raslan Darawsheh net/tap: fix reported number of Tx packets
>> c2c15f769 Rosen Xu app/testpmd: fix shaper profile parameters
>> c1752a36b Sachin Saxena net/dpaa: fix link speed based on MAC type
>> 6bdf14455 Thomas Monjalon eal/x86: remove unused memcpy file
>> 66908eff1 Tiwei Bie net/virtio: add missing supported features
>> f457e9007 Tiwei Bie net/virtio-user: do not stop stopped device again
next prev parent reply other threads:[~2019-01-15 16:42 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 [this message]
[not found] ` <54CBAA185211B4429112C315DA58FF6D3369EBA7@IRSMSX103.ger.corp.intel.com>
2019-01-14 19:37 ` Yongseok Koh
2019-01-17 0:13 ` dwilder
-- 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=EBB56169-F642-4CC1-8E80-EA9ADC1050C1@mellanox.com \
--to=yskoh@mellanox.com \
--cc=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=jerinj@marvell.com \
--cc=marchana@marvell.com \
--cc=pathreya@marvell.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).