From: Simon Horman <simon.horman@corigine.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next 2/5] devlink: Allow modification of devlink ops
Date: Wed, 29 Sep 2021 12:20:13 +0200 [thread overview]
Message-ID: <20210929102012.GE13506@corigine.com> (raw)
In-Reply-To: <0e07ad986db7d2f033a97e4c8253940676128237.1632909221.git.leonro@nvidia.com>
On Wed, Sep 29, 2021 at 01:16:36PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Drop const identifier from devlink_ops declaration to allow
> run-time modification of pre-declared ops.
>
> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Thanks, for NFP portion:
Acked-by: Simon Horman <simon.horman@corigine.com>
next prev parent reply other threads:[~2021-09-29 10:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 10:16 [Intel-wired-lan] [PATCH net-next 0/5] Devlink reload and missed notifications fix Leon Romanovsky
2021-09-29 10:16 ` [Intel-wired-lan] [PATCH net-next 1/5] devlink: Add missed notifications iterators Leon Romanovsky
2021-09-29 10:16 ` [Intel-wired-lan] [PATCH net-next 2/5] devlink: Allow modification of devlink ops Leon Romanovsky
2021-09-29 10:20 ` Simon Horman [this message]
2021-09-29 10:16 ` [Intel-wired-lan] [PATCH net-next 3/5] devlink: Allow set specific ops callbacks dynamically Leon Romanovsky
2021-09-29 10:38 ` Dan Carpenter
2021-09-29 10:43 ` Leon Romanovsky
2021-09-29 10:16 ` [Intel-wired-lan] [PATCH net-next 4/5] net/mlx5: Register separate reload devlink ops for multiport device Leon Romanovsky
2021-09-29 10:16 ` [Intel-wired-lan] [PATCH net-next 5/5] devlink: Delete reload enable/disable interface Leon Romanovsky
2021-09-29 10:40 ` [Intel-wired-lan] [PATCH net-next 0/5] Devlink reload and missed notifications fix Leon Romanovsky
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=20210929102012.GE13506@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