From: "Íñigo Huguet" <ihuguet@redhat.com>
To: ecree.xilinx@gmail.com, habetsm.xilinx@gmail.com
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, cmclachlan@solarflare.com, brouer@redhat.com,
netdev@vger.kernel.org, "Íñigo Huguet" <ihuguet@redhat.com>
Subject: [PATCH net v2 0/2] sfc: fix some efx_separate_tx_channels errors
Date: Fri, 27 May 2022 10:05:27 +0200 [thread overview]
Message-ID: <20220527080529.24225-1-ihuguet@redhat.com> (raw)
Trying to load sfc driver with modparam efx_separate_tx_channels=1
resulted in errors during initialization and not being able to use the
NIC. This patches fix a few bugs and make it work again.
v2:
* added Martin's patch instead of a previous mine. Mine one solved some
of the initialization errors, but Martin's solves them also in all
possible cases.
* removed whitespaces cleanup, as requested by Jakub
Martin Habets (1):
sfc: fix considering that all channels have TX queues
Íñigo Huguet (1):
sfc: fix wrong tx channel offset with efx_separate_tx_channels
drivers/net/ethernet/sfc/efx_channels.c | 6 ++----
drivers/net/ethernet/sfc/net_driver.h | 2 +-
2 files changed, 3 insertions(+), 5 deletions(-)
--
2.34.1
next reply other threads:[~2022-05-27 8:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 8:05 Íñigo Huguet [this message]
2022-05-27 8:05 ` [PATCH net v2 1/2] sfc: fix considering that all channels have TX queues Íñigo Huguet
2022-05-27 8:05 ` [PATCH net v2 2/2] sfc: fix wrong tx channel offset with efx_separate_tx_channels Íñigo Huguet
2022-05-29 11:20 ` [PATCH net v2 0/2] sfc: fix some efx_separate_tx_channels errors patchwork-bot+netdevbpf
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=20220527080529.24225-1-ihuguet@redhat.com \
--to=ihuguet@redhat.com \
--cc=brouer@redhat.com \
--cc=cmclachlan@solarflare.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=habetsm.xilinx@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).