From: Kevin Traynor <ktraynor@redhat.com>
To: "Zhu, TaoX" <taox.zhu@intel.com>, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to LTS release 18.11.6
Date: Wed, 4 Dec 2019 10:49:02 +0000 [thread overview]
Message-ID: <5d9522f5-e79d-db3a-e3a1-cd3435d0b225@redhat.com> (raw)
In-Reply-To: <60652C6914E08D41B9AA1580751B3CA9C13F53@SHSMSX106.ccr.corp.intel.com>
On 04/12/2019 01:57, Zhu, TaoX wrote:
> The patch should not be backported:
>
> dbda2092d Tao Zhu net/i40e: fix request queue in VF
>
Thanks for confirming, will drop from list.
Kevin.
> BR,
> Zhu, Tao
>
>
>> -----Original Message-----
>> From: Kevin Traynor [mailto:ktraynor@redhat.com]
>> Sent: Wednesday, December 4, 2019 3:07 AM
>> Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>; Akhil Goyal
>> <akhil.goyal@nxp.com>; Burakov, Anatoly <anatoly.burakov@intel.com>;
>> Arnon Warshavsky <arnon@qwilt.com>; David Marchand
>> <david.marchand@redhat.com>; Dekel Peled <dekelp@mellanox.com>;
>> Dharmik Thakkar <dharmik.thakkar@arm.com>; Gavin Hu
>> <gavin.hu@arm.com>; Harman Kalra <hkalra@marvell.com>; Hemant
>> Agrawal <hemant.agrawal@nxp.com>; Honnappa Nagarahalli
>> <honnappa.nagarahalli@arm.com>; Igor Russkikh
>> <igor.russkikh@aquantia.com>; Kalesh AP <kalesh-
>> anakkur.purayil@broadcom.com>; Ananyev, Konstantin
>> <konstantin.ananyev@intel.com>; Lance Richardson
>> <lance.richardson@broadcom.com>; Liu, Yong <yong.liu@intel.com>; Matan
>> Azrad <matan@mellanox.com>; Maxime Coquelin
>> <maxime.coquelin@redhat.com>; Chautru, Nicolas
>> <nicolas.chautru@intel.com>; Nipun Gupta <nipun.gupta@nxp.com>; Pavel
>> Belous <pavel.belous@aquantia.com>; Zhang, Qi Z <qi.z.zhang@intel.com>;
>> Rahul Gupta <rahul.gupta@broadcom.com>; Remy Horton
>> <remy.horton@intel.com>; Pattan, Reshma <reshma.pattan@intel.com>;
>> Ruifeng Wang <ruifeng.wang@arm.com>; Sachin Saxena
>> <sachin.saxena@nxp.com>; Santoshkumar Karanappa Rastapur
>> <santosh.rastapur@broadcom.com>; Somnath Kotur
>> <somnath.kotur@broadcom.com>; Stephen Hemminger
>> <stephen@networkplumber.org>; Zhu, TaoX <taox.zhu@intel.com>; Venkat
>> Duvvuru <venkatkumar.duvvuru@broadcom.com>; Viacheslav Ovsiienko
>> <viacheslavo@mellanox.com>; Zhao1, Wei <wei.zhao1@intel.com>; Xiaoyu
>> Min <jackmin@mellanox.com>; Wang, Yipeng1 <yipeng1.wang@intel.com>
>> Subject: please help backporting some patches to LTS release 18.11.6
>>
>> Hi commit authors (and maintainers),
>>
>> I didn't apply following commits from DPDK master to 18.11 LTS branch, as
>> conflicts or build errors occur.
>>
>> Can authors check your patches in the following list and either:
>> - Backport your patches to the 18.11 branch, or
>> - Indicate that the patch should not be backported
>>
>> Some notes on LTS backports:
>>
>> A backport should contain a reference to the DPDK master branch commit in
>> it's commit message in the following fashion:
>> [ upstream commit <commit's dpdk master branch SHA-1 checksum> ]
>>
>> For example:
>> https://git.dpdk.org/dpdk-
>> stable/commit/?h=18.11&id=d90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb
>>
>> When sending the backported patch, please indicate the target branch in the
>> subject line, as we have multiple branches, for example:
>> [PATCH 18.11] foo/bar: fix baz
>>
>> With git format-patch, this can be achieved by appending the parameter:
>> --subject-prefix='PATCH 18.11'
>>
>> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
>>
>> FYI, branch 18.11 is located at tree:
>> https://git.dpdk.org/dpdk-stable
>>
>> Thanks.
>>
>> Kevin.
>>
>> ---
>> c023cd5b2 Ajit Khaparde net/bnxt: fix async link handling and update
>> fe7848521 Ajit Khaparde net/bnxt: fix doorbell register offset for Tx ring
>> 89278c59d Ajit Khaparde net/bnxt: fix flow flush handling
>> 458f0360e Ajit Khaparde net/bnxt: get default HWRM command timeout
>> from FW
>> 305d1fd39 Ajit Khaparde net/bnxt: update trusted VF status only when it
>> changes
>> b149a7064 Anatoly Burakov eal/freebsd: add config reattach in secondary
>> process
>> 75dbb45f2 Arnon Warshavsky eal: fix mapping leak in secondary process
>> ea81c1b81 Dekel Peled net/mlx5: fix NVGRE matching
>> 9d10f53e4 Harman Kalra test/metrics: fix second run
>> 0964a9512 Hemant Agrawal bus/dpaa: fix dpaa_sec blacklist
>> 2967612f4 Hemant Agrawal test/crypto: fix session init failure for wireless
>> case
>> b0437f8b0 Honnappa Nagarahalli hash: load value after full key compare
>> 6f43682e0 Honnappa Nagarahalli test/hash: init parameters in the correct
>> function
>> e0d865357 Kalesh AP net/bnxt: enable interrupts according interface
>> status
>> 1f3cea004 Kalesh AP net/bnxt: fix check of address mapping
>> 996355970 Kalesh AP net/bnxt: fix coding style
>> 2171e66f9 Kalesh AP net/bnxt: fix deferred start of Tx queues
>> 324c56551 Kalesh AP net/bnxt: fix error checking of FW commands
>> 9bc556e3e Kalesh AP net/bnxt: fix error handling in xstats
>> 96b0931d5 Kalesh AP net/bnxt: fix extended port counter statistics
>> dc177579d Kalesh AP net/bnxt: fix L2 context calculation for Thor
>> 3955e2687 Kalesh AP net/bnxt: fix Rx queue start/stop
>> 988562f0b Kalesh AP net/bnxt: fix setting default MAC address
>> 9f55e6ac7 Kalesh AP net/bnxt: fix stats errors handling
>> aa2c00702 Kalesh AP net/bnxt: fix traffic stall on Rx queue stop/start
>> 72aaa312e Kalesh AP net/bnxt: fix VF probe when MAC address is zero
>> 9924dfd60 Kalesh AP net/bnxt: move macro definitions to header file
>> a135e050a Konstantin Ananyev examples/ipsec-secgw: fix packet length
>> 94d4afd2d Lance Richardson net/bnxt: advertise scatter Rx offload capability
>> e76097f84 Marvin Liu net/virtio: cleanup on demand when in-order Tx
>> 1ae55ad38 Marvin Liu net/virtio: fix mbuf data and packet length
>> mismatch
>> 721c95301 Matan Azrad net/mlx5: fix Rx scatter mode validation
>> 6d608a6cc Nicolas Chautru baseband/fpga_lte_fec: fix probing
>> 005d943e5 Nipun Gupta net/dpaa2: set port in mbuf
>> e9924638f Pavel Belous net/atlantic: add FW mailbox guard mutex
>> 34c0ba839 Rahul Gupta net/bnxt: fix Rx queue count
>> e9ccabda0 Rahul Gupta net/bnxt: reduce cleanup time during reset
>> recovery
>> 09aac391a Santoshkumar Karanappa Rastapur net/bnxt: fix forwarding with
>> higher mbuf size
>> b4e190d55 Santoshkumar Karanappa Rastapur net/bnxt: fix MAC/VLAN filter
>> allocation
>> d6c7475b9 Santoshkumar Karanappa Rastapur net/bnxt: free default
>> completion ring before VF config
>> 5526c8025 Somnath Kotur net/bnxt: fix race between interrupt handler
>> and dev config
>> f35eaaca5 Stephen Hemminger net/bnxt: fix crash in secondary process
>> dbda2092d Tao Zhu net/i40e: fix request queue in VF
>> 6118503d8 Venkat Duvvuru net/bnxt: fix VLAN filtering
>> dcfbc594f Wei Zhao net/iavf: fix queue interrupt for ice
>
next prev parent reply other threads:[~2019-12-04 10:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191203190657.22859-1-ktraynor@redhat.com>
2019-12-04 1:57 ` Zhu, TaoX
2019-12-04 10:49 ` Kevin Traynor [this message]
2019-12-11 7:36 ` Arnon Warshavsky
2019-12-11 9:05 ` Kevin Traynor
2019-12-12 11:58 Kevin Traynor
2019-12-17 10:06 ` Somnath Kotur
2019-12-17 11:06 ` Kevin Traynor
2019-12-17 14:04 ` Kevin Traynor
2019-12-17 14:10 ` Somnath Kotur
2019-12-18 6:26 ` Somnath Kotur
2019-12-18 11:10 ` Kevin Traynor
2019-12-19 3:31 ` Somnath Kotur
-- strict thread matches above, loose matches on Subject: below --
2019-12-03 19:43 Kevin Traynor
2019-12-03 19:58 ` Kevin Traynor
2019-12-03 20:18 ` Ajit Khaparde
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=5d9522f5-e79d-db3a-e3a1-cd3435d0b225@redhat.com \
--to=ktraynor@redhat.com \
--cc=stable@dpdk.org \
--cc=taox.zhu@intel.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).