patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
	Somnath Kotur <somnath.kotur@broadcom.com>
Cc: dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to LTS release 18.11.6
Date: Tue, 3 Dec 2019 19:58:30 +0000	[thread overview]
Message-ID: <8b9a3e43-bbbd-896e-63a7-09e00aa2b402@redhat.com> (raw)
In-Reply-To: <20191203194327.23717-1-ktraynor@redhat.com>

Hi Ajit and Somnath,

On 03/12/2019 19:43, Kevin Traynor wrote:
> 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.
> 

There are a lot of bnxt fixes going to master over the last while, but
many of them won't apply to 18.11 branch, or apply and cause a build
failure (see below). I can do straightforward rebases as I am applying
but with the amount of difference between branches, it means most won't
apply and need the author/bnxt maintainers to send backports.

I will continue to attempt to apply any new fixes best effort, but if
there are fixes you want on the 18.11 branch that don't apply, please
send dedicated backports for the branch.

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
> 


  reply	other threads:[~2019-12-03 19:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03 19:43 Kevin Traynor
2019-12-03 19:58 ` Kevin Traynor [this message]
2019-12-03 20:18   ` Ajit Khaparde
     [not found] <20191203190657.22859-1-ktraynor@redhat.com>
2019-12-04  1:57 ` Zhu, TaoX
2019-12-04 10:49   ` Kevin Traynor
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

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=8b9a3e43-bbbd-896e-63a7-09e00aa2b402@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=somnath.kotur@broadcom.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).