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 0/2] sfc/siena: fix some efx_separate_tx_channels errors
Date: Tue, 31 May 2022 15:40:32 +0200 [thread overview]
Message-ID: <20220531134034.389792-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.
This has been already done in sfc, do it also in sfc_siena.
Martin Habets (1):
sfc/siena: fix considering that all channels have TX queues
Íñigo Huguet (1):
sfc/siena: fix wrong tx channel offset with efx_separate_tx_channels
drivers/net/ethernet/sfc/siena/efx_channels.c | 6 ++----
drivers/net/ethernet/sfc/siena/net_driver.h | 2 +-
2 files changed, 3 insertions(+), 5 deletions(-)
--
2.34.1
next reply other threads:[~2022-05-31 13:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 13:40 Íñigo Huguet [this message]
2022-05-31 13:40 ` [PATCH net 1/2] sfc/siena: fix considering that all channels have TX queues Íñigo Huguet
2022-05-31 13:40 ` [PATCH net 2/2] sfc/siena: fix wrong tx channel offset with efx_separate_tx_channels Íñigo Huguet
2022-05-31 15:37 ` [PATCH net 0/2] sfc/siena: fix some efx_separate_tx_channels errors Jakub Kicinski
2022-06-01 6:23 ` Íñigo Huguet
2022-06-01 6:36 ` [PATCH net v2 " Íñigo Huguet
2022-06-01 6:36 ` [PATCH net v2 1/2] sfc/siena: fix considering that all channels have TX queues Íñigo Huguet
2022-06-01 6:36 ` [PATCH net v2 2/2] sfc/siena: fix wrong tx channel offset with efx_separate_tx_channels Íñigo Huguet
2022-06-01 7:20 ` Martin Habets
2022-06-02 1:00 ` [PATCH net v2 0/2] sfc/siena: 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=20220531134034.389792-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.