patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: stable@dpdk.org
Cc: bluca@debian.org, david.marchand@redhat.com,
	john.mcnamara@intel.com, qi.z.zhang@intel.com,
	jie1x.wang@intel.com, Jingjing Wu <jingjing.wu@intel.com>,
	Beilei Xing <beilei.xing@intel.com>
Subject: Re: [PATCH 21.11] Revert "net/iavf: add thread for event callbacks"
Date: Mon, 19 Dec 2022 10:16:23 +0000	[thread overview]
Message-ID: <70479d78-5d96-a7c4-e76b-d8787f8a6421@redhat.com> (raw)
In-Reply-To: <20221215105729.480368-1-ktraynor@redhat.com>

On 15/12/2022 10:57, Kevin Traynor wrote:
> This reverts commit fcf8e69afb79eede8d14f8f5e16c6212d5c2dbfe.
> 
> Reverting this commit as it has just been backported for
> 21.11.3 but an issue has been identified. A fix is in
> progress but it is not ready in time for 21.11.3.
> 
> It is better to revert the patch and keep the behaviour in
> 21.11.3 the same as 21.11/21.11.1/21.11.2 and do a correct
> chain of fixes in a later release when they are available.
> 
> Link to discussion upstream patch being discussed [1] and for
> reference commit id of patch being reverted in DPDK main
> branch [2].
> 
> [1]
> https://mails.dpdk.org/archives/dev/2022-November/256458.html
> [2]
> commit cb5c1b91f76f ("net/iavf: add thread for event callbacks")
> 
> Signed-off-by: Kevin Traynor<ktraynor@redhat.com>
> ---

Applied and pushed to 21.11 branch. Thanks.


      reply	other threads:[~2022-12-19 10:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 10:57 Kevin Traynor
2022-12-19 10:16 ` Kevin Traynor [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=70479d78-5d96-a7c4-e76b-d8787f8a6421@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=beilei.xing@intel.com \
    --cc=bluca@debian.org \
    --cc=david.marchand@redhat.com \
    --cc=jie1x.wang@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=qi.z.zhang@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
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).