From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 2/2] net/bnxt: fix link handling and configuration
Date: Thu, 9 Nov 2017 17:15:22 -0800 [thread overview]
Message-ID: <fb4c442b-08b2-238e-2327-ae7d98f980fd@intel.com> (raw)
In-Reply-To: <20171109174628.44636-2-ajit.khaparde@broadcom.com>
On 11/9/2017 9:46 AM, Ajit Khaparde wrote:
> Remove a case where we were sending a depricated field to the FW.
> There is no need to send auto_link_speed to the FW.
> Also set the auto_mode correctly depending on the setting requested.
>
> Fixes: 7bc8e9a227cc ("net/bnxt: support async link notification")
>
> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
Hi Ajit,
What is the scope of these fixes? How critical are they?
I am for postponing them into next release.
We should stop somewhere to get patches, normally they have been sent later than
initial planned release date.
<...>
next prev parent reply other threads:[~2017-11-10 1:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 17:46 [dpdk-dev] [PATCH 1/2] net/bnxt: fix duplicate creation of ntuple filter Ajit Khaparde
2017-11-09 17:46 ` [dpdk-dev] [PATCH 2/2] net/bnxt: fix link handling and configuration Ajit Khaparde
2017-11-10 1:15 ` Ferruh Yigit [this message]
2017-11-10 9:54 ` [dpdk-dev] [PATCH 1/2] net/bnxt: fix duplicate creation of ntuple filter Ferruh Yigit
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=fb4c442b-08b2-238e-2327-ae7d98f980fd@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@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).