From: patchwork-bot+netdevbpf@kernel•org
To: Leon Romanovsky <leon@kernel•org>
Cc: davem@davemloft•net, kuba@kernel•org, leonro@nvidia•com,
huangguangbin2@huawei•com, jacob.e.keller@intel•com,
jiri@nvidia•com, linux-kernel@vger•kernel.org,
netdev@vger•kernel.org, salil.mehta@huawei•com,
snelson@pensando•io, yisen.zhuang@huawei•com,
moyufeng@huawei•com
Subject: Re: [PATCH net-next 0/6] Devlink cleanup for delay event series
Date: Sat, 14 Aug 2021 13:10:06 +0000 [thread overview]
Message-ID: <162894660670.3097.4150652110351873021.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1628933864.git.leonro@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Sat, 14 Aug 2021 12:57:25 +0300 you wrote:
> From: Leon Romanovsky <leonro@nvidia•com>
>
> Hi,
>
> Jakub's request to make sure that devlink events are delayed and not
> printed till they fully accessible [1] requires us to implement delayed
> event notification system in the devlink.
>
> [...]
Here is the summary with links:
- [net-next,1/6] devlink: Simplify devlink_pernet_pre_exit call
https://git.kernel.org/netdev/net-next/c/cbf6ab672eb4
- [net-next,2/6] devlink: Remove check of always valid devlink pointer
https://git.kernel.org/netdev/net-next/c/7ca973dc9fe5
- [net-next,3/6] devlink: Count struct devlink consumers
https://git.kernel.org/netdev/net-next/c/437ebfd90a25
- [net-next,4/6] devlink: Use xarray to store devlink instances
https://git.kernel.org/netdev/net-next/c/11a861d767cd
- [net-next,5/6] devlink: Clear whole devlink_flash_notify struct
https://git.kernel.org/netdev/net-next/c/ed43fbac7178
- [net-next,6/6] net: hns3: remove always exist devlink pointer check
https://git.kernel.org/netdev/net-next/c/a1fcb106ae97
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-08-14 13:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-14 9:57 [PATCH net-next 0/6] Devlink cleanup for delay event series Leon Romanovsky
2021-08-14 9:57 ` [PATCH net-next 1/6] devlink: Simplify devlink_pernet_pre_exit call Leon Romanovsky
2021-08-14 9:57 ` [PATCH net-next 2/6] devlink: Remove check of always valid devlink pointer Leon Romanovsky
2021-08-14 9:57 ` [PATCH net-next 3/6] devlink: Count struct devlink consumers Leon Romanovsky
2021-08-16 15:47 ` Jakub Kicinski
2021-08-16 15:53 ` Leon Romanovsky
2021-08-16 16:07 ` Jakub Kicinski
2021-08-16 21:32 ` Keller, Jacob E
2021-08-18 8:12 ` Leon Romanovsky
2021-08-18 17:50 ` Keller, Jacob E
2021-08-20 13:06 ` Leon Romanovsky
2021-08-20 20:23 ` Keller, Jacob E
2021-08-18 8:03 ` Leon Romanovsky
2021-08-14 9:57 ` [PATCH net-next 4/6] devlink: Use xarray to store devlink instances Leon Romanovsky
2021-08-16 21:27 ` Keller, Jacob E
2021-08-14 9:57 ` [PATCH net-next 5/6] devlink: Clear whole devlink_flash_notify struct Leon Romanovsky
2021-08-16 21:29 ` Keller, Jacob E
2021-08-14 9:57 ` [PATCH net-next 6/6] net: hns3: remove always exist devlink pointer check Leon Romanovsky
2021-08-14 13:10 ` patchwork-bot+netdevbpf [this message]
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=162894660670.3097.4150652110351873021.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=huangguangbin2@huawei$(echo .)com \
--cc=jacob.e.keller@intel$(echo .)com \
--cc=jiri@nvidia$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=leon@kernel$(echo .)org \
--cc=leonro@nvidia$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=moyufeng@huawei$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=salil.mehta@huawei$(echo .)com \
--cc=snelson@pensando$(echo .)io \
--cc=yisen.zhuang@huawei$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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