From: oulijun <oulijun@huawei.com> To: dpdk stable <stable@dpdk.org> Cc: Brian Johnson <brian.johnson@intel.com>, Chenbo Xia <chenbo.xia@intel.com>, Chengchang Tang <tangchengchang@huawei.com>, "Jerin Jacob" <jerinj@marvell.com>, Jesse Brandeburg <jesse.brandeburg@intel.com>, Konstantin Ananyev <konstantin.ananyev@intel.com>, Matan Azrad <matan@nvidia.com>, Maxime Coquelin <maxime.coquelin@redhat.com>, "Nithin Dabilpuram" <ndabilpuram@marvell.com>, Patrick Fu <patrick.fu@intel.com>, "Qi Zhang" <qi.z.zhang@intel.com>, Xueming Li <xuemingl@nvidia.com> Subject: Re: [dpdk-stable] please help backporting some patches to stable release 19.11.6 Date: Mon, 23 Nov 2020 09:53:07 +0800 Message-ID: <9bdf4113-1eab-84c9-f244-dabe4d7697ce@huawei.com> (raw) In-Reply-To: <20201109190556.3481033-1-luca.boccassi@gmail.com> 在 2020/11/10 3:05, luca.boccassi@gmail.com 写道: > Hi commit authors (and maintainers), > > I didn't apply following commits from DPDK main to 19.11 > stable branch, as conflicts or build errors occur. > > Can authors check your patches in the following list and either: > - Backport your patches to the 19.11 branch, or > - Indicate that the patch should not be backported > > Please do either of the above by the 16th of November. > > > Some notes on stable backports: > > A backport should contain a reference to the DPDK main branch commit > in it's commit message in the following fashion: > [ upstream commit <commit's dpdk main 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 19.11] foo/bar: fix baz > > With git format-patch, this can be achieved by appending the parameter: > --subject-prefix='PATCH 19.11' > > Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org". > > FYI, branch 19.11 is located at tree: > https://git.dpdk.org/dpdk-stable > > Thanks. > > Luca Boccassi > > --- > 0e98d5e6d9 Chengchang Tang net/hns3: fix packet type report in Rx > f9edada651 Chengchang Tang net/hns3: fix Tx checksum outer header prepare > fb6eb9009f Chengchang Tang net/hns3: fix Tx checksum with fixed header length Hi,Luca Boccassi I have returned the hns3 patchset on November 13, which contains two patches and the dependent patches. Can you help you integrate them? Thanks Lijun Ou > ead06572bd Jesse Brandeburg net/iavf: fix performance with writeback policy > c59898131b Maxime Coquelin vhost: validate index in async API > 364eb0e466 Nithin Dabilpuram net/octeontx2: avoid per packet barrier with multi segment > fb4b7a131c Patrick Fu vhost: fix guest/host physical address conversion > 1cbdad1bf2 Xueming Li common/mlx5: get number of ports that can be bonded > . >
next prev parent reply other threads:[~2020-11-23 1:53 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-09 19:05 luca.boccassi [not found] ` <20201109190556.3481033-1-luca.boccassi@gmail.com> 2020-11-12 9:19 ` Fu, Patrick 2020-11-12 9:38 ` Luca Boccassi 2020-11-23 1:53 ` oulijun [this message] -- strict thread matches above, loose matches on Subject: below -- 2020-11-25 9:07 luca.boccassi 2020-11-17 11:28 luca.boccassi [not found] <20201102194256.1910550-1-luca.boccassi@gmail.com> 2020-11-02 19:43 ` luca.boccassi 2020-11-03 9:06 ` oulijun 2020-11-03 15:04 ` Ruifeng Wang 2020-11-04 8:42 ` Wangxiaoyun (Cloud)
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=9bdf4113-1eab-84c9-f244-dabe4d7697ce@huawei.com \ --to=oulijun@huawei.com \ --cc=brian.johnson@intel.com \ --cc=chenbo.xia@intel.com \ --cc=jerinj@marvell.com \ --cc=jesse.brandeburg@intel.com \ --cc=konstantin.ananyev@intel.com \ --cc=matan@nvidia.com \ --cc=maxime.coquelin@redhat.com \ --cc=ndabilpuram@marvell.com \ --cc=patrick.fu@intel.com \ --cc=qi.z.zhang@intel.com \ --cc=stable@dpdk.org \ --cc=tangchengchang@huawei.com \ --cc=xuemingl@nvidia.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
patches for DPDK stable branches This inbox may be cloned and mirrored by anyone: git clone --mirror http://inbox.dpdk.org/stable/0 stable/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 stable stable/ http://inbox.dpdk.org/stable \ stable@dpdk.org public-inbox-index stable Example config snippet for mirrors. Newsgroup available over NNTP: nntp://inbox.dpdk.org/inbox.dpdk.stable AGPL code for this site: git clone https://public-inbox.org/public-inbox.git