From: "Yury M." <yurypm@arista.com>
To: Michael Chan <michael.chan@broadcom.com>,
Pavan Chebbi <pavan.chebbi@broadcom.com>
Cc: mchan@broadcom.com, netdev@vger.kernel.org,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tg3: guard napi_disable and pci_disable_device calls
Date: Mon, 18 May 2026 17:44:34 +0100 [thread overview]
Message-ID: <8ea0f79a-a8b0-4d1e-85dc-6f5b8fd3c135@arista.com> (raw)
In-Reply-To: <CACKFLikhxsYc6zP2ksV4=_MwZDLC=6Q2rD9CGwEACKOiVgXBhw@mail.gmail.com>
Yes, mostly this patch is about adding a flag to track the NAPI status
to avoid a double release.
On 5/18/26 17:27, Michael Chan wrote:
> On Mon, May 18, 2026 at 8:43 AM Pavan Chebbi <pavan.chebbi@broadcom.com> wrote:
>
>> I am not sure if we should allow this fix for what I think is a
>> situation arising out of an unsupported topology..
>> I will defer this to Michael or netdev maintainers for their feedback.
> If the question is about adding a driver flag to keep track of the
> NAPI state, I think it should be ok. bnxt has a similar
> BNXT_STATE_NAPI_DISABLED flag for this purpose.
next prev parent reply other threads:[~2026-05-18 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 10:58 Yury Murashka
2026-05-15 15:42 ` Pavan Chebbi
2026-05-18 11:13 ` Yury M.
[not found] ` <a120c9f5-5818-4335-ac2c-caaf4f6f4fc7@arista.com>
2026-05-18 15:43 ` Pavan Chebbi
2026-05-18 16:27 ` Michael Chan
2026-05-18 16:44 ` Yury M. [this message]
2026-05-19 10:09 ` Pavan Chebbi
2026-05-18 16:37 ` Yury M.
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=8ea0f79a-a8b0-4d1e-85dc-6f5b8fd3c135@arista.com \
--to=yurypm@arista.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.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
all inboxes | Powered by JetHome®