From: Leon Romanovsky <leon@kernel.org>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next v1 0/5] Devlink reload and missed notifications fix
Date: Wed, 29 Sep 2021 17:20:01 +0300 [thread overview]
Message-ID: <YVR2EYrklpj+CSfo@unreal> (raw)
In-Reply-To: <20210929065621.20cb08ad@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On Wed, Sep 29, 2021 at 06:56:21AM -0700, Jakub Kicinski wrote:
> On Wed, 29 Sep 2021 13:46:38 +0000 Vladimir Oltean wrote:
> > On Wed, Sep 29, 2021 at 06:40:04AM -0700, Jakub Kicinski wrote:
> > > Swapping ops is a nasty hack in my book.
> > >
> > > And all that to avoid having two op structures in one driver.
> > > Or to avoid having counters which are always 0?
> > >
> > > Sorry, at the very least you need better explanation for this.
> >
> > Leon, while the discussion about this unfolds, can you please repost
> > patch 1 separately? :)
>
> Yes, please and thanks! :)
Done, thanks
https://lore.kernel.org/netdev/2ed1159291f2a589b013914f2b60d8172fc525c1.1632925030.git.leonro at nvidia.com/T/#u
next prev parent reply other threads:[~2021-09-29 14:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 12:00 [Intel-wired-lan] [PATCH net-next v1 0/5] Devlink reload and missed notifications fix Leon Romanovsky
2021-09-29 12:00 ` [Intel-wired-lan] [PATCH net-next v1 1/5] devlink: Add missed notifications iterators Leon Romanovsky
2021-09-29 13:29 ` Vladimir Oltean
2021-09-29 12:00 ` [Intel-wired-lan] [PATCH net-next v1 2/5] devlink: Allow modification of devlink ops Leon Romanovsky
2021-09-29 12:00 ` [Intel-wired-lan] [PATCH net-next v1 3/5] devlink: Allow set specific ops callbacks dynamically Leon Romanovsky
2021-09-29 12:25 ` Greg Kroah-Hartman
2021-09-29 12:58 ` Leon Romanovsky
2021-09-29 12:00 ` [Intel-wired-lan] [PATCH net-next v1 4/5] net/mlx5: Register separate reload devlink ops for multiport device Leon Romanovsky
2021-09-29 13:55 ` Jakub Kicinski
2021-09-29 14:16 ` Leon Romanovsky
2021-09-29 14:26 ` Jakub Kicinski
2021-09-29 14:31 ` Leon Romanovsky
2021-09-29 14:35 ` Jakub Kicinski
2021-09-29 15:24 ` Leon Romanovsky
2021-09-29 12:00 ` [Intel-wired-lan] [PATCH net-next v1 5/5] devlink: Delete reload enable/disable interface Leon Romanovsky
2021-09-29 13:40 ` [Intel-wired-lan] [PATCH net-next v1 0/5] Devlink reload and missed notifications fix Jakub Kicinski
2021-09-29 13:46 ` Vladimir Oltean
2021-09-29 13:56 ` Jakub Kicinski
2021-09-29 14:20 ` Leon Romanovsky [this message]
2021-09-29 14:13 ` Leon Romanovsky
2021-09-29 14:39 ` Jakub Kicinski
2021-09-29 15:31 ` Leon Romanovsky
2021-09-29 17:55 ` Jakub Kicinski
2021-09-29 19:11 ` 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=YVR2EYrklpj+CSfo@unreal \
--to=leon@kernel.org \
--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