From: Somnath Kotur <somnath.kotur@broadcom.com>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: dpdk stable <stable@dpdk.org>,
Ajit Kumar Khaparde <ajit.khaparde@broadcom.com>,
Kalesh Anakkur Purayil <kalesh-anakkur.purayil@broadcom.com>,
Santoshkumar Karanappa Rastapur <santosh.rastapur@broadcom.com>,
Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com>
Subject: Re: [dpdk-stable] please help backporting some patches to LTS release 18.11.6
Date: Tue, 17 Dec 2019 19:40:24 +0530 [thread overview]
Message-ID: <CAOBf=muOCShL6ZD4bPdSBDSyb6aTp+eqOZ_m22U3FnDfnBb2Mg@mail.gmail.com> (raw)
In-Reply-To: <f8f1376d-29c5-bfa4-3706-7bae38e5f7e6@redhat.com>
Oh ok sure will do
Thanks
Som
On Tue, 17 Dec 2019, 19:34 Kevin Traynor, <ktraynor@redhat.com> wrote:
> On 17/12/2019 11:06, Kevin Traynor wrote:
> > On 17/12/2019 10:06, Somnath Kotur wrote:
> >> Hi Kevin,
> >> Out of the 30 bnxt patches that you have identified for
> >> 18.11, we have managed to rebase 25 of them to a total of 19
> >> patches(some of them squashed)
> >> which i will be sending as a patch-set to dpdk-stable soon (before
> >> your EOD Dec 18th)
> >>
>
> One other thing, no problem to squash patches if it makes sense, but
> please have a reference to each of the master commit ids in the commit
> log. That way it is easy to cross reference now and in future which
> commits are backported.
>
> thanks,
> Kevin.
>
> e.g.
> commit 0c97c2c11cb9408f35cebbb6aaf94ed45671ccbc
> Author: Xiao Zhang <xiao.zhang@intel.com>
> Date: Mon Jul 22 23:11:52 2019 +0800
>
> net/e1000: fix i219 hang on reset/close
>
> [ upstream commit 1fc9701238edcf0541289b9ae15565b6d9d7ab30]
> [ upstream commit 675f65dc660805eff1953e3dfb6242ec076a9444]
>
>
> >
> > Thanks Somnath, this is great to hear. Just one request - there have
> > been a lot of patches queued last week and pushed this week, so can you
> > check that your rebases are still ok with the current dpdk-stable:18.11
> > branch.
> >
> >> The commits that won't be backported for 18.11 are
> >>
> >> e9ccabda0 Rahul Gupta net/bnxt: reduce cleanup time during reset
> recovery
> >> 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
> >> 037cc747d Venkat Duvvuru net/bnxt: fix default MAC check
> >> 6118503d8 Venkat Duvvuru net/bnxt: fix VLAN filtering
> >>
> >
> > Sure, I will remove them from list
> >
> > thanks,
> > Kevin.
> >
> >>
> >>
> >> Thanks
> >> Som
> >>
> >>
> >> On Thu, Dec 12, 2019 at 5:29 PM Kevin Traynor <ktraynor@redhat.com>
> 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. Note, it may be
> >>> dependent on another patch below that has also not been applied.
> >>>
> >>> 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
> >>>
> >>> Please do either of the above by 12/18/19.
> >>>
> >>> 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.
> >>>
> >>> ---
> >>> 1fc3b3f06 Adrian Moreno vhost: convert buffer addresses to GPA for
> logging
> >>> c023cd5b2 Ajit Khaparde net/bnxt: fix async link handling and
> update
> >>> 21b1f1abe Ajit Khaparde net/bnxt: fix COS queue mapping
> >>> 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
> >>> 6d3f9917f Anatoly Burakov eal: fix memory config allocation for
> multi-process
> >>> b149a7064 Anatoly Burakov eal/freebsd: add config reattach in
> secondary process
> >>> 6080796f6 Anatoly Burakov mem: make base address hint OS specific
> >>> be048a1aa Andrew Rybchenko net/virtio: fix descriptor addressed in Tx
> >>> 1526dd053 Andrew Rybchenko net/virtio: fix Tx checksum offloads
> >>> 7bbc7dc43 Andrzej Ostruszka net/dpaa2: fix possible use of
> uninitialized vars
> >>> 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
> >>> 05817057f Igor Chauskin net/ena: fix indication of bad L4 Rx
> checksums
> >>> 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
> >>> f5019a53d Kalesh AP net/bnxt: fix memory leak
> >>> 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
> >>> 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
> >>> ce4fd609b Nipun Gupta net/dpaa2: add retry and timeout in packet
> enqueue API
> >>> 005d943e5 Nipun Gupta net/dpaa2: set port in mbuf
> >>> 0da362b8f Nipun Gupta raw/dpaa2_cmdif: add retry and timeout in
> packet enqueue API
> >>> 9e0d81c1a Ori Kam net/mlx5: fix selection between encap and
> decap
> >>> 7392ad06f Pavan Nikhilesh app/testpmd: use better randomness for Tx
> split
> >>> e9924638f Pavel Belous net/atlantic: add FW mailbox guard mutex
> >>> f0617163b Radu Bulie mempool/dpaa2: report error on endless
> loop in mbuf release
> >>> 34c0ba839 Rahul Gupta net/bnxt: fix Rx queue count
> >>> e9ccabda0 Rahul Gupta net/bnxt: reduce cleanup time during reset
> recovery
> >>> 8937597cf Santoshkumar Karanappa Rastapur net/bnxt: fix crash after
> removing and adding slaves
> >>> 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
> >>> 037cc747d Venkat Duvvuru net/bnxt: fix default MAC check
> >>> 6118503d8 Venkat Duvvuru net/bnxt: fix VLAN filtering
> >>> dcfbc594f Wei Zhao net/iavf: fix queue interrupt for ice
> >>> 6977f1451 Wisam Jaddo app/testpmd: fix missing GENEVE item in
> raw encap
> >>> 8e2f25cf3 Xiaoyu Min net/mlx5: fix crash on hash Rx queue
> handling for drop
> >>> fba321301 Xiaoyu Min net/mlx5: improve flow item IP validation
> >>>
> >>
> >
>
>
next prev parent reply other threads:[~2019-12-17 14:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2019-12-18 6:26 ` Somnath Kotur
2019-12-18 11:10 ` Kevin Traynor
2019-12-19 3:31 ` Somnath Kotur
[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
-- 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='CAOBf=muOCShL6ZD4bPdSBDSyb6aTp+eqOZ_m22U3FnDfnBb2Mg@mail.gmail.com' \
--to=somnath.kotur@broadcom.com \
--cc=ajit.khaparde@broadcom.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=ktraynor@redhat.com \
--cc=santosh.rastapur@broadcom.com \
--cc=stable@dpdk.org \
--cc=venkatkumar.duvvuru@broadcom.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).