From: Orgad Shaneh <orgads@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Wei Hu <weh@microsoft.com>,
Long Li <longli@kernel.org>,
stable@dpdk.org
Subject: Re: [PATCH 2/2] net/mana: fix Rx interrupt enable failing on lock contention
Date: Mon, 2 Nov 2026 08:27:56 +0000 [thread overview]
Message-ID: <20261102082756.835327-1-orgads@gmail.com> (raw)
In-Reply-To: <20261102091202.180b9eb5@stephen-xps.local>
Stephen Hemminger <stephen@networkplumber.org> wrote:
> > Fixes: 077ca514d641 ("net/mana: support device reset")
> > Cc: stable@dpdk.org
>
> Since this code didnt go into a previous stable release
> doing cc to stable is not needed
Right, reset support is only in 26.07. Please drop the Cc: stable
when applying, or I can send a v2 without it if you prefer.
1/2 fixes code from 22.11, so I left Cc: stable there.
On the AI review of this patch: reset_ops_lock is a default-type,
non-robust mutex, so pthread_mutex_lock() cannot return an error
here, and the existing calls in the reset path do not check it
either.
The iol-unit-arm64 failure is memif_pmd_autotest crashing on
Fedora 44, which this patch does not touch.
Recheck-request: iol-unit-arm64-testing
Thanks,
Orgad
prev parent reply other threads:[~2026-11-04 12:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 7:08 [PATCH 1/2] net/mana: fix Rx interrupt vector beyond device count Orgad Shaneh
2026-11-02 7:08 ` [PATCH 2/2] net/mana: fix Rx interrupt enable failing on lock contention Orgad Shaneh
2026-11-02 8:12 ` Stephen Hemminger
2026-11-02 8:27 ` Orgad Shaneh [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=20261102082756.835327-1-orgads@gmail.com \
--to=orgads@gmail.com \
--cc=dev@dpdk.org \
--cc=longli@kernel.org \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=weh@microsoft.com \
/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