patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "Yu, DapengX" <dapengx.yu@intel.com>,
	"Yu, PingX" <pingx.yu@intel.com>,  dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] It there plan to queue this patch to stable release 19.11.9
Date: Thu, 3 Jun 2021 07:38:54 +0200	[thread overview]
Message-ID: <CAATJJ0LzsgT6f7d1mE9Z+tEjQTAEJ63KAydkmOyHKgA1upB5bQ@mail.gmail.com> (raw)
In-Reply-To: <6340038.7RWX4JVtyS@thomas>

On Mon, May 31, 2021 at 5:01 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 31/05/2021 11:21, Christian Ehrhardt:
> > On Wed, May 26, 2021 at 5:13 AM Yu, DapengX <dapengx.yu@intel.com> wrote:
> > > This patch: http://mails.dpdk.org/archives/stable/2021-March/029204.html
> >
> > This patch actually was never merged in the main branch
> > On main we have:
> >
> > commit f93949c3afc39b0f610e0661f7baa21060ada13a
> > Author: Haiyue Wang <haiyue.wang@intel.com>
> > net/ice: fix memory leak on dev closed
> >
> > This one also refers to bd513ece3c40 for a fix and was in 19.11 already.
> > Then quite similar to what you referred to, but a more generic (all
> > drivers) fix on the main branch
> >
> > commit 30410493759f4bae3f65497737661e27b93c2d0e
> > Author: Thomas Monjalon <thomas@monjalon.net>
> > drivers/net: check process type in close operation
> > See => https://github.com/DPDK/dpdk/commit/30410493759f4bae3f65497737661e27b93c2d0e
> >
> > This one was in 20.11 but not targeted for stable@dpdk.org
> >
> > The patch almost applies but since the change is mostly the same to
> > all drivers it seems backportable.
> >
> > Maybe if you could sync with Thomas if this (general) solution is
> > applicable and prepare the backport we can add it.
> > It is close as I wanted to call for RC1 already, but if done soon it
> > should be fine.
> > I'll hold back 19.11.9-RC1 another day to give this a chance to be
> > clarified until tomorrow.
> >
> > @Dapeng please talk to Thomas and consider providing a 19.11.9
> > backport of the fix that made it into the main branch.
> > @Thomas Monjalon was there a specific reason/prereq which made you not
> > targeting stable@ with the fix?
>
> It was not considered as a fix but a behaviour improvement :)
> I agree it could be backported.

FYI - by now it is backported and part of the WIP 19.11.9

>


-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd

      reply	other threads:[~2021-06-03  5:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DM5PR11MB1401AD92A56AAE00675730B08C249@DM5PR11MB1401.namprd11.prod.outlook.com>
2021-05-31  9:21 ` Christian Ehrhardt
2021-05-31 10:00   ` Yu, DapengX
2021-05-31 15:01   ` Thomas Monjalon
2021-06-03  5:38     ` Christian Ehrhardt [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=CAATJJ0LzsgT6f7d1mE9Z+tEjQTAEJ63KAydkmOyHKgA1upB5bQ@mail.gmail.com \
    --to=christian.ehrhardt@canonical.com \
    --cc=dapengx.yu@intel.com \
    --cc=pingx.yu@intel.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).