From: Simon Horman <simon.horman@corigine.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next v1] devlink: Make devlink_register to be void
Date: Wed, 22 Sep 2021 14:01:05 +0200 [thread overview]
Message-ID: <20210922120105.GA2994@corigine.com> (raw)
In-Reply-To: <311a6c7e74ad612474446890a12c9d310b9507ed.1632300324.git.leonro@nvidia.com>
On Wed, Sep 22, 2021 at 11:58:03AM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> devlink_register() can't fail and always returns success, but all drivers
> are obligated to check returned status anyway. This adds a lot of boilerplate
> code to handle impossible flow.
>
> Make devlink_register() void and simplify the drivers that use that
> API call.
>
> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
NFP portion:
Acked-by: Simon Horman <simon.horman@corigine.com>
next prev parent reply other threads:[~2021-09-22 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 8:58 [Intel-wired-lan] [PATCH net-next v1] devlink: Make devlink_register to be void Leon Romanovsky
2021-09-22 12:01 ` Simon Horman [this message]
2021-09-22 12:05 ` Vladimir Oltean
2021-09-22 12:15 ` Jiri Pirko
2021-09-22 13:20 ` patchwork-bot+netdevbpf
2021-09-22 13:22 ` 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=20210922120105.GA2994@corigine.com \
--to=simon.horman@corigine.com \
--cc=intel-wired-lan@osuosl.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