From: jgh@redhat.com
To: netdev@vger.kernel.org
Cc: Jeremy Harris <jgh@redhat.com>
Subject: [RFC PATCH 6/7] drivers: net: bnx2: NIC driver Rx ring ECN
Date: Wed, 11 Jan 2023 14:34:26 +0000 [thread overview]
Message-ID: <20230111143427.1127174-7-jgh@redhat.com> (raw)
In-Reply-To: <20230111143427.1127174-1-jgh@redhat.com>
From: Jeremy Harris <jgh@redhat.com>
Reformat local variables as reverse-christmas-tree.
No functional change.
Signed-off-by: Jeremy Harris <jgh@redhat.com>
---
drivers/net/ethernet/broadcom/bnx2.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/broadcom/bnx2.c b/drivers/net/ethernet/broadcom/bnx2.c
index 9f473854b0f4..f55ac9c7b6fd 100644
--- a/drivers/net/ethernet/broadcom/bnx2.c
+++ b/drivers/net/ethernet/broadcom/bnx2.c
@@ -3141,10 +3141,10 @@ bnx2_get_hw_rx_cons(struct bnx2_napi *bnapi)
static int
bnx2_rx_int(struct bnx2 *bp, struct bnx2_napi *bnapi, int budget)
{
- struct bnx2_rx_ring_info *rxr = &bnapi->rx_ring;
u16 hw_cons, sw_cons, sw_ring_cons, sw_prod, sw_ring_prod;
- struct l2_fhdr *rx_hdr;
+ struct bnx2_rx_ring_info *rxr = &bnapi->rx_ring;
int rx_pkt = 0, pg_ring_used = 0;
+ struct l2_fhdr *rx_hdr;
if (budget <= 0)
return rx_pkt;
--
2.39.0
next prev parent reply other threads:[~2023-01-11 14:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 14:34 [RFC PATCH net-next 0/7] NIC driver Rx ring ECN jgh
2023-01-11 14:34 ` [RFC PATCH 1/7] net: NIC driver Rx ring ECN: skbuff and tcp support jgh
2023-01-11 14:34 ` [RFC PATCH 2/7] net: NIC driver Rx ring ECN: stats counter jgh
2023-01-11 14:34 ` [RFC PATCH 3/7] drivers: net: xgene: NIC driver Rx ring ECN jgh
2023-01-11 14:34 ` [RFC PATCH 4/7] drivers: net: bnx2x: " jgh
2023-01-11 14:34 ` [RFC PATCH 5/7] " jgh
2023-01-11 14:34 ` jgh [this message]
2023-01-11 14:34 ` [RFC PATCH 7/7] drivers: net: bnx2: " jgh
2023-01-11 18:46 ` [RFC PATCH net-next 0/7] " Jakub Kicinski
2023-01-12 14:06 ` Jeremy Harris
2023-01-13 0:09 ` Jakub Kicinski
2023-01-19 17:05 ` Jeremy Harris
2023-01-19 17:20 ` Jakub Kicinski
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=20230111143427.1127174-7-jgh@redhat.com \
--to=jgh@redhat.com \
--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).