From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Edwin Brossette <edwin.brossette@6wind.com>
Cc: dev@dpdk.org, somnath.kotur@broadcom.com,
Didier Pallard <didier.pallard@6wind.com>,
Olivier Matz <olivier.matz@6wind.com>,
Kalesh Anakkur Purayil <kalesh-anakkur.purayil@broadcom.com>
Subject: Re: net/bnxt: wrong link status when lsc_intr is used
Date: Thu, 19 Jan 2023 17:04:39 -0800 [thread overview]
Message-ID: <CACZ4nhtJDV60xD-1tE7Dhkd7xyKnKH37OT5EA1Nx1U6DD=6isQ@mail.gmail.com> (raw)
In-Reply-To: <CANDF9xBL_YZxX+rHqMO4Oahm080_D2+DVP81wEVz-M+3uyBOEQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 477 bytes --]
On Thu, Jan 19, 2023 at 5:37 AM Edwin Brossette
<edwin.brossette@6wind.com> wrote:
>
> Hello,
>
:::: snip ::::
> I was wondering if patching the code to move this line which sets lsc interrupt on somewhere else might be reasonable, or if this could cause further trouble. Maybe having a parameter to trigger it ON/OFF might be a good addition.
> May I have your opinion on this matter?
We will check and get back to you on this.
Thanks
Ajit
>
> Sincerely,
> Edwin Brossette
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4218 bytes --]
next prev parent reply other threads:[~2023-01-20 1:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 13:37 Edwin Brossette
2023-01-20 1:04 ` Ajit Khaparde [this message]
2023-01-31 5:08 ` Somnath Kotur
2023-02-06 8:44 ` Edwin Brossette
2023-02-07 2:07 ` Somnath Kotur
2023-02-06 17:11 ` [PATCH] bnxt: fix unwanted interrupt config on link state change edwin.brossette
2023-02-07 5:44 ` Somnath Kotur
2023-02-08 18:19 ` Ajit Khaparde
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='CACZ4nhtJDV60xD-1tE7Dhkd7xyKnKH37OT5EA1Nx1U6DD=6isQ@mail.gmail.com' \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=didier.pallard@6wind.com \
--cc=edwin.brossette@6wind.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=olivier.matz@6wind.com \
--cc=somnath.kotur@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;
as well as URLs for NNTP newsgroup(s).