patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Somnath Kotur <somnath.kotur@broadcom.com>,
	dpdk stable <stable@dpdk.org>
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>,
	Akhil Goyal <akhil.goyal@nxp.com>,
	Anatoly Burakov <anatoly.burakov@intel.com>,
	Andrew Rybchenko <arybchenko@solarflare.com>,
	Anoob Joseph <anoobj@marvell.com>,
	Archana Muniganti <marchana@marvell.com>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Chunsong Feng <fengchunsong@huawei.com>,
	David Marchand <david.marchand@redhat.com>,
	Dekel Peled <dekelp@mellanox.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	Gagandeep Singh <g.singh@nxp.com>,
	Harman Kalra <hkalra@marvell.com>,
	Huisong Li <lihuisong@huawei.com>,
	Igor Chauskin <igorch@amazon.com>, Itsuro Oda <oda@valinux.co.jp>,
	Kalesh AP <kalesh-anakkur.purayil@broadcom.com>,
	Konstantin Ananyev <konstantin.ananyev@intel.com>,
	Maciej Bielski <mba@semihalf.com>,
	Marvin Liu <yong.liu@intel.com>, Matan Azrad <matan@mellanox.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Michal Krawczyk <mk@semihalf.com>, Min Hu <humin29@huawei.com>,
	Min Wang <wangmin3@huawei.com>, Nikhil Rao <nikhil.rao@intel.com>,
	Nipun Gupta <nipun.gupta@nxp.com>, Ori Kam <orika@mellanox.com>,
	Pavan Nikhilesh <pbhagavatula@marvell.com>,
	Qi Zhang <qi.z.zhang@intel.com>,
	Radu Bulie <radu-andrei.bulie@nxp.com>,
	Rahul Gupta <rahul.gupta@broadcom.com>,
	Raslan Darawsheh <rasland@mellanox.com>,
	Remy Horton <remy.horton@intel.com>,
	Reshma Pattan <reshma.pattan@intel.com>,
	Santoshkumar Karanappa Rastapur <santosh.rastapur@broadcom.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Tao Zhu <taox.zhu@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Tiwei Bie <tiwei.bie@intel.com>,
	Viacheslav Ovsiienko <viacheslavo@mellanox.com>,
	Wei Hu <xavier.huwei@huawei.com>, Wei Zhao <wei.zhao1@intel.com>,
	Wisam Jaddo <wisamm@mellanox.com>,
	Xiaoyu Min <jackmin@mellanox.com>,
	Yinan Wang <yinan.wang@intel.com>
Subject: Re: [dpdk-stable] please help backporting some patches to LTS release 18.11.7
Date: Wed, 18 Mar 2020 22:58:42 +0000	[thread overview]
Message-ID: <ecf1755f-fdd1-3728-d3b5-ddb68ea353f8@redhat.com> (raw)
In-Reply-To: <CAOBf=mvqhUCWDzzaQFZz3h4bvNQD24WykbYC2oVkcTQqrm0eiQ@mail.gmail.com>

On 18/03/2020 05:58, Somnath Kotur wrote:
> On Fri, Mar 6, 2020 at 10:23 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 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 03/13/20.
>>
>> Some notes on LTS backports:
>>
>> A backport should contain a reference to the DPDK master branch commit
>> in it's commit message in exactly 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.
>>
>> ---
> Hi Kevin,
>             Only the following 4 bnxt patches will be needed, have
> just sent the backported versions of these patches to stable@dpdk.org
> 
>  f35eaaca5  Stephen Hemminger net/bnxt: fix crash in secondary process
>  d9fc6a0d0  Kalesh AP        net/bnxt: fix probe in FreeBSD
>  8f3224f26  Kalesh AP        net/bnxt: fix IOVA mapping
>  975ff25e7  Rahul Gupta      net/bnxt: fix default timeout for getting
> FW version
> 
> Thanks a lot!
> 

Thanks Somnath, I will apply these and remove the other bnxt patches
from the list.

> -Som
> 


      reply	other threads:[~2020-03-18 22:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-06 16:52 Kevin Traynor
2020-03-09  4:21 ` Itsuro ODA
2020-03-18 22:57   ` Kevin Traynor
2020-03-13 21:49 ` Kevin Traynor
2020-03-18  5:58 ` Somnath Kotur
2020-03-18 22:58   ` Kevin Traynor [this message]

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=ecf1755f-fdd1-3728-d3b5-ddb68ea353f8@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=akhil.goyal@nxp.com \
    --cc=anatoly.burakov@intel.com \
    --cc=anoobj@marvell.com \
    --cc=arybchenko@solarflare.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dekelp@mellanox.com \
    --cc=fengchunsong@huawei.com \
    --cc=ferruh.yigit@intel.com \
    --cc=g.singh@nxp.com \
    --cc=hkalra@marvell.com \
    --cc=humin29@huawei.com \
    --cc=igorch@amazon.com \
    --cc=jackmin@mellanox.com \
    --cc=kalesh-anakkur.purayil@broadcom.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=lihuisong@huawei.com \
    --cc=marchana@marvell.com \
    --cc=matan@mellanox.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=mba@semihalf.com \
    --cc=mk@semihalf.com \
    --cc=nikhil.rao@intel.com \
    --cc=nipun.gupta@nxp.com \
    --cc=oda@valinux.co.jp \
    --cc=orika@mellanox.com \
    --cc=pbhagavatula@marvell.com \
    --cc=qi.z.zhang@intel.com \
    --cc=radu-andrei.bulie@nxp.com \
    --cc=rahul.gupta@broadcom.com \
    --cc=rasland@mellanox.com \
    --cc=remy.horton@intel.com \
    --cc=reshma.pattan@intel.com \
    --cc=santosh.rastapur@broadcom.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=taox.zhu@intel.com \
    --cc=thomas@monjalon.net \
    --cc=tiwei.bie@intel.com \
    --cc=viacheslavo@mellanox.com \
    --cc=wangmin3@huawei.com \
    --cc=wei.zhao1@intel.com \
    --cc=wisamm@mellanox.com \
    --cc=xavier.huwei@huawei.com \
    --cc=yinan.wang@intel.com \
    --cc=yong.liu@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).