From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Ilya Maximets <i.maximets@ovn.org>
Cc: dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to stable release 19.11.9
Date: Tue, 18 May 2021 07:29:33 +0200 [thread overview]
Message-ID: <CAATJJ0Jn_q9NvFBP5vkEQXWpubYPTS6cpTEpvzaFwhZiUn25wQ@mail.gmail.com> (raw)
In-Reply-To: <5c2bb6d8-fa07-e17b-efab-65d67bfe43a6@ovn.org>
On Mon, May 17, 2021 at 8:46 PM Ilya Maximets <i.maximets@ovn.org> wrote:
>
> 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
Thanks Ilya,
Yeah - I'm not trial&error'ing every 20.11 backport, but I'm totally
fine to merge those once pointed to them by the Author.
> or should
> I rebase and send a version for 19.11 specifically?
>
> Bets regards, Ilya Maximets.
--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
next prev parent reply other threads:[~2021-05-18 5:30 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
2021-05-18 5:29 ` Christian Ehrhardt [this message]
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=CAATJJ0Jn_q9NvFBP5vkEQXWpubYPTS6cpTEpvzaFwhZiUn25wQ@mail.gmail.com \
--to=christian.ehrhardt@canonical.com \
--cc=i.maximets@ovn.org \
--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).