From: Jakub Kicinski <kuba@kernel.org>
To: Simon Horman <simon.horman@corigine.com>
Cc: David Miller <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, oss-drivers@corigine.com,
Yinjun Zhang <yinjun.zhang@corigine.com>,
Fei Qin <fei.qin@corigine.com>
Subject: Re: [PATCH net-next v2 0/5] nfp: support FEC mode reporting and auto-neg
Date: Fri, 30 Sep 2022 18:47:35 -0700 [thread overview]
Message-ID: <20220930184735.62aa0781@kernel.org> (raw)
In-Reply-To: <20220929085832.622510-1-simon.horman@corigine.com>
On Thu, 29 Sep 2022 10:58:27 +0200 Simon Horman wrote:
> this series adds support for the following features to the nfp driver:
>
> * Patch 1/5: Support active FEC mode
> * Patch 2/5: Don't halt driver on non-fatal error when interacting with fw
> * Patch 3/5: Treat port independence as a firmware rather than port property
> * Patch 4/5: Support link auto negotiation
> * Patch 5/5: Support restart of link auto negotiation
Looks better, thanks for the changes.
BTW shouldn't the sp_indiff symbol be prefixed by _pf%u ?
That's not really introduced by this series tho.
next prev parent reply other threads:[~2022-10-01 1:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 8:58 [PATCH net-next v2 0/5] nfp: support FEC mode reporting and auto-neg Simon Horman
2022-09-29 8:58 ` [PATCH net-next v2 1/5] nfp: add support for reporting active FEC mode Simon Horman
2022-09-29 8:58 ` [PATCH net-next v2 2/5] nfp: avoid halt of driver init process when non-fatal error happens Simon Horman
2022-09-29 8:58 ` [PATCH net-next v2 3/5] nfp: refine the ABI of getting `sp_indiff` info Simon Horman
2022-09-29 8:58 ` [PATCH net-next v2 4/5] nfp: add support for link auto negotiation Simon Horman
2022-09-29 8:58 ` [PATCH net-next v2 5/5] nfp: add support restart of link auto-negotiation Simon Horman
2022-10-01 1:47 ` Jakub Kicinski [this message]
2022-10-03 8:41 ` [PATCH net-next v2 0/5] nfp: support FEC mode reporting and auto-neg Yinjun Zhang
2022-10-03 20:01 ` Jakub Kicinski
2022-10-04 2:04 ` Yinjun Zhang
2022-10-01 2:20 ` 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=20220930184735.62aa0781@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=fei.qin@corigine.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.com \
--cc=yinjun.zhang@corigine.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.