patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <>
To: "Yu, DapengX" <>,
	Christian Ehrhardt <>
Cc: "Yu, PingX" <>, dpdk stable <>
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: <>

31/05/2021 11:21, Christian Ehrhardt:
> On Wed, May 26, 2021 at 5:13 AM Yu, DapengX <> wrote:
> > This patch:
> This patch actually was never merged in the main branch
> On main we have:
> commit f93949c3afc39b0f610e0661f7baa21060ada13a
> Author: Haiyue Wang <>
> 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 <>
> drivers/net: check process type in close operation
> See =>
> This one was in 20.11 but not targeted for
> 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] <>
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6340038.7RWX4JVtyS@thomas \ \ \ \ \ \

* 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 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/ \
	public-inbox-index stable

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone