From: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Shagun Agarwal <shaguna@chelsio.com>,
Indranil Choudhury <indranil@chelsio.com>,
Nirranjan Kirubaharan <nirranjan@chelsio.com>,
"stable@dpdk.org" <stable@dpdk.org>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <luca.boccassi@att.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] net/cxgbe: fix init failure due to new flash parts
Date: Wed, 18 Jul 2018 15:17:15 +0530 [thread overview]
Message-ID: <20180718094713.GA27283@chelsio.com> (raw)
In-Reply-To: <c5adf11e-898e-7c10-1770-b45e838ecd42@intel.com>
On Wednesday, July 07/18/18, 2018 at 14:56:12 +0530, Ferruh Yigit wrote:
> On 7/9/2018 4:43 PM, Rahul Lakkireddy wrote:
> > Add decode logic for new flash parts shipped with new Chelsio NICs
> > to fix initialization failure on these NICs.
> >
> > Cc: stable@dpdk.org
>
> I guess Fixes not added intentionally since this is not fixing a previous code
> but fixing a behavior with new flash parts, but fix is required to be
> backported. Please reply with a Fixes line if this is not correct.
>
Correct. Fixes line was not added intentionally. It's not fixing
any bug with previous code, but rather adding decode logic to detect
the Chelsio NICs with new flash parts. Without this patch, CXGBE PMD
fails to initialize on these new Chelsio NICs with new flash parts.
This fix needs to be backported to allow CXGBE PMD in stable releases
also to detect and initialize on these new Chelsio NICs.
Thanks,
Rahul
prev parent reply other threads:[~2018-07-18 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 15:43 [dpdk-dev] " Rahul Lakkireddy
2018-07-18 9:26 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2018-07-18 9:47 ` Rahul Lakkireddy [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=20180718094713.GA27283@chelsio.com \
--to=rahul.lakkireddy@chelsio.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=indranil@chelsio.com \
--cc=ktraynor@redhat.com \
--cc=luca.boccassi@att.com \
--cc=nirranjan@chelsio.com \
--cc=shaguna@chelsio.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).