patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ilya Maximets <i.maximets@ovn.org>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: i.maximets@ovn.org, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to stable release 19.11.9
Date: Mon, 17 May 2021 20:46:12 +0200
Message-ID: <5c2bb6d8-fa07-e17b-efab-65d67bfe43a6@ovn.org> (raw)
In-Reply-To: <20210517182104.3335577-1-christian.ehrhardt@canonical.com>

On 5/17/21 8:21 PM, Christian Ehrhardt wrote:
> 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.
> 
> To authors, could you please 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 05/24/21.
> 

...

> 23abee9dea  Ilya Maximets    net/virtio: fix interrupt unregistering for listening socket

Hi.  I've sent a backport of this patch for 20.11 earlier today:
  
  https://inbox.dpdk.org/stable/20210517124500.143341-1-i.maximets@ovn.org/

It can be applied on top of 19.11 branch with 3-way merge, i.e.
`git am -3 <patch>` works fine.  Will that work for you or should
I rebase and send a version for 19.11 specifically?

Bets regards, Ilya Maximets.

       reply	other threads:[~2021-05-17 18:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210517182104.3335577-1-christian.ehrhardt@canonical.com>
2021-05-17 18:46 ` Ilya Maximets [this message]
2021-05-18  5:29   ` Christian Ehrhardt
2021-05-19 17:14 ` Slava Ovsiienko
2021-05-20  9:17 ` David Marchand
2021-06-03  5:02   ` Christian Ehrhardt
     [not found] <20210520075556.1969082-1-christian.ehrhardt@canonical.com>
2021-05-20  9:59 ` Kalesh Anakkur Purayil
2021-05-20 13:53   ` Christian Ehrhardt
2021-05-21  7:47     ` Kalesh Anakkur Purayil
2021-05-21  9:03 ` Huang, Wei

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=5c2bb6d8-fa07-e17b-efab-65d67bfe43a6@ovn.org \
    --to=i.maximets@ovn.org \
    --cc=christian.ehrhardt@canonical.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

patches for DPDK stable branches

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://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/ https://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