From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: David Marchand <david.marchand@redhat.com>,
dpdk-dev <dev@dpdk.org>, dpdk stable <stable@dpdk.org>,
Somnath Kotur <somnath.kotur@broadcom.com>,
Randy Schacher <stuart.schacher@broadcom.com>,
Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
Subject: Re: [PATCH] net/bnxt: fix compatibility with some old firmwares
Date: Tue, 17 May 2022 20:58:04 -0700 [thread overview]
Message-ID: <CACZ4nhuVfyzwwgX7+Te=v0hU-C8rWMSRADCOj0g-kaze6egFbQ@mail.gmail.com> (raw)
In-Reply-To: <2184715.HovnAMPojK@thomas>
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
On Tue, May 17, 2022 at 12:18 AM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 30/03/2022 01:21, Ajit Khaparde:
> > On Fri, Mar 18, 2022 at 8:03 AM David Marchand
> > <david.marchand@redhat.com> wrote:
> > >
> > > This reverts commit 3972281f47b2cc0cf844698885f0e6b4228c0975.
> > >
> > > Reported by Red Hat QE: with older firmware versions (at least versions
> > > 20.6.112.0 and 20.6.143.0), initialisation never succeeds following this
> > > change.
> > > Revert it for now, waiting for a more complete fix.
> > >
> > > Fixes: 3972281f47b2 ("net/bnxt: fix device readiness check")
> > > Cc: stable@dpdk.org
> > >
> > > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> >
> > Patch applied to dpdk-next-net-brcm. Thanks
>
> It seems this patch has been lost.
> I don't find it in dpdk-next-net-brcm.
Hmm.. Yes.
I pushed it again. Please check. Thanks
>
>
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4218 bytes --]
next prev parent reply other threads:[~2022-05-18 3:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 15:03 David Marchand
2022-03-29 23:21 ` Ajit Khaparde
2022-05-17 7:18 ` Thomas Monjalon
2022-05-18 3:58 ` Ajit Khaparde [this message]
2022-05-18 6:22 ` Thomas Monjalon
2022-05-23 0:46 ` 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='CACZ4nhuVfyzwwgX7+Te=v0hU-C8rWMSRADCOj0g-kaze6egFbQ@mail.gmail.com' \
--to=ajit.khaparde@broadcom.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=somnath.kotur@broadcom.com \
--cc=stable@dpdk.org \
--cc=stuart.schacher@broadcom.com \
--cc=thomas@monjalon.net \
/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).