patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Yu, DapengX" <dapengx.yu@intel.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: "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: Mon, 31 May 2021 17:01:15 +0200
Message-ID: <6340038.7RWX4JVtyS@thomas> (raw)
In-Reply-To: <CAATJJ0KZoBnkQQ278vi6LpiQoA36KuKhjhwCquH0cUwm+uMb+A@mail.gmail.com>

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.



  parent reply	other threads:[~2021-05-31 15:01 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 [this message]
2021-06-03  5:38     ` Christian Ehrhardt

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=6340038.7RWX4JVtyS@thomas \
    --to=thomas@monjalon.net \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dapengx.yu@intel.com \
    --cc=pingx.yu@intel.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