All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leonro@nvidia.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next 0/5] Devlink reload and missed notifications fix
Date: Wed, 29 Sep 2021 13:40:51 +0300	[thread overview]
Message-ID: <YVRCs1+09G0g40N8@unreal> (raw)
In-Reply-To: <cover.1632909221.git.leonro@nvidia.com>

On Wed, Sep 29, 2021 at 01:16:34PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
> 
> Hi,
> 
> This series starts from the fixing the bug introduced by implementing
> devlink delayed notifications logic, where I missed some of the
> notifications functions.
> 
> The rest series provides a way to dynamically set devlink ops that is
> needed for mlx5 multiport device and starts cleanup by removing
> not-needed logic.
> 
> In the next series, we will delete various publish API, drop general
> lock, annotate the code and rework logic around devlink->lock.
> 
> All this is possible because driver initialization is separated from the
> user input now.
> 
> Thanks
> 
> Leon Romanovsky (5):
>   devlink: Add missed notifications iterators

I missed WARN_ON(), I'm resending the series.

Thanks

WARNING: multiple messages have this Message-ID (diff)
From: Leon Romanovsky <leonro@nvidia.com>
To: "David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Andrew Lunn <andrew@lunn.ch>, Ariel Elior <aelior@marvell.com>,
	Bin Luo <luobin9@huawei.com>,
	Claudiu Manoil <claudiu.manoil@nxp.com>,
	Coiby Xu <coiby.xu@gmail.com>,
	Derek Chickles <dchickles@marvell.com>, <drivers@pensando.io>,
	Eric Dumazet <eric.dumazet@gmail.com>,
	Felix Manlunas <fmanlunas@marvell.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	"Geetha sowjanya" <gakula@marvell.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	<GR-everest-linux-l2@marvell.com>, <GR-Linux-NIC-Dev@marvell.com>,
	hariprasad <hkelam@marvell.com>, Ido Schimmel <idosch@nvidia.com>,
	<intel-wired-lan@lists.osuosl.org>,
	Ioana Ciornei <ioana.ciornei@nxp.com>,
	Jerin Jacob <jerinj@marvell.com>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Jiri Pirko <jiri@nvidia.com>,
	Jonathan Lemon <jonathan.lemon@gmail.com>,
	Linu Cherian <lcherian@marvell.com>,
	<linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>,
	<linux-rdma@vger.kernel.org>, <linux-staging@lists.linux.dev>,
	Manish Chopra <manishc@marvell.com>,
	Michael Chan <michael.chan@broadcom.com>,
	"Moshe Shemesh" <moshe@nvidia.com>, <netdev@vger.kernel.org>,
	<oss-drivers@corigine.com>,
	Richard Cochran <richardcochran@gmail.com>,
	"Saeed Mahameed" <saeedm@nvidia.com>,
	Salil Mehta <salil.mehta@huawei.com>,
	"Satanand Burla" <sburla@marvell.com>,
	Shannon Nelson <snelson@pensando.io>,
	Shay Drory <shayd@nvidia.com>,
	Simon Horman <simon.horman@corigine.com>,
	"Subbaraya Sundeep" <sbhatta@marvell.com>,
	Sunil Goutham <sgoutham@marvell.com>,
	"Taras Chornyi" <tchornyi@marvell.com>,
	Tariq Toukan <tariqt@nvidia.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	<UNGLinuxDriver@microchip.com>,
	Vadym Kochan <vkochan@marvell.com>,
	Vivien Didelot <vivien.didelot@gmail.com>,
	"Vladimir Oltean" <vladimir.oltean@nxp.com>,
	Yisen Zhuang <yisen.zhuang@huawei.com>
Subject: Re: [PATCH net-next 0/5] Devlink reload and missed notifications fix
Date: Wed, 29 Sep 2021 13:40:51 +0300	[thread overview]
Message-ID: <YVRCs1+09G0g40N8@unreal> (raw)
In-Reply-To: <cover.1632909221.git.leonro@nvidia.com>

On Wed, Sep 29, 2021 at 01:16:34PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
> 
> Hi,
> 
> This series starts from the fixing the bug introduced by implementing
> devlink delayed notifications logic, where I missed some of the
> notifications functions.
> 
> The rest series provides a way to dynamically set devlink ops that is
> needed for mlx5 multiport device and starts cleanup by removing
> not-needed logic.
> 
> In the next series, we will delete various publish API, drop general
> lock, annotate the code and rework logic around devlink->lock.
> 
> All this is possible because driver initialization is separated from the
> user input now.
> 
> Thanks
> 
> Leon Romanovsky (5):
>   devlink: Add missed notifications iterators

I missed WARN_ON(), I'm resending the series.

Thanks

  parent reply	other threads:[~2021-09-29 10:40 UTC|newest]

Thread overview: 20+ 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 ` 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   ` 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:16   ` Leon Romanovsky
2021-09-29 10:20   ` [Intel-wired-lan] " Simon Horman
2021-09-29 10:20     ` Simon Horman
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:16   ` Leon Romanovsky
2021-09-29 10:38   ` [Intel-wired-lan] " Dan Carpenter
2021-09-29 10:38     ` Dan Carpenter
2021-09-29 10:43     ` [Intel-wired-lan] " Leon Romanovsky
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   ` 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:16   ` Leon Romanovsky
2021-09-29 10:40 ` Leon Romanovsky [this message]
2021-09-29 10:40   ` [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=YVRCs1+09G0g40N8@unreal \
    --to=leonro@nvidia.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 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.