From: Sudarsana Reddy Kalluru <sudarsana.kalluru@qlogic.com>
To: <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <Yuval.Mintz@qlogic.com>,
<sudarsana.kalluru@qlogic.com>
Subject: [PATCH net-next 1/4] qed: Reset the enable flag for eth protocol.
Date: Mon, 23 May 2016 05:17:40 -0400 [thread overview]
Message-ID: <1463995063-25560-2-git-send-email-sudarsana.kalluru@qlogic.com> (raw)
In-Reply-To: <1463995063-25560-1-git-send-email-sudarsana.kalluru@qlogic.com>
This patch fixes the coding error in determining the enable flag for
the application/protocol. The enable flag should be enable for all the
protocols but the eth.
Signed-off-by: Sudarsana Reddy Kalluru <sudarsana.kalluru@qlogic.com>
Signed-off-by: Yuval Mintz <Yuval.Mintz@qlogic.com>
---
drivers/net/ethernet/qlogic/qed/qed_dcbx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/qlogic/qed/qed_dcbx.c b/drivers/net/ethernet/qlogic/qed/qed_dcbx.c
index cbf58e1..2685b353 100644
--- a/drivers/net/ethernet/qlogic/qed/qed_dcbx.c
+++ b/drivers/net/ethernet/qlogic/qed/qed_dcbx.c
@@ -221,7 +221,7 @@ qed_dcbx_process_tlv(struct qed_hwfn *p_hwfn,
* indication, but we only got here if there was an
* app tlv for the protocol, so dcbx must be enabled.
*/
- enable = !!(type == DCBX_PROTOCOL_ETH);
+ enable = !(type == DCBX_PROTOCOL_ETH);
qed_dcbx_update_app_info(p_data, p_hwfn, enable, true,
priority, tc, type);
--
1.8.3.1
next prev parent reply other threads:[~2016-05-23 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 9:17 [PATCH net-next 0/4] qed/qede support for dcbnl Sudarsana Reddy Kalluru
2016-05-23 9:17 ` Sudarsana Reddy Kalluru [this message]
2016-05-23 9:17 ` [PATCH net-next 2/4] qed: Add support for query/config dcbx Sudarsana Reddy Kalluru
2016-05-23 9:17 ` [PATCH net-next 3/4] qed: Add dcbnl support Sudarsana Reddy Kalluru
2016-05-23 9:17 ` [PATCH net-next 4/4] qede: " Sudarsana Reddy Kalluru
2016-05-23 22:10 ` [PATCH net-next 0/4] qed/qede support for dcbnl David Miller
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=1463995063-25560-2-git-send-email-sudarsana.kalluru@qlogic.com \
--to=sudarsana.kalluru@qlogic.com \
--cc=Yuval.Mintz@qlogic.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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).