From: patchwork-bot+netdevbpf@kernel.org
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: jiri@resnulli.us, netdev@vger.kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
shannon.nelson@amd.com, michael.chan@broadcom.com,
cai.huoqing@linux.dev, george.cherian@marvell.com,
danieller@nvidia.com, moshe@nvidia.com, saeedm@nvidia.com,
aelior@marvell.com, manishc@marvell.com, irusskikh@marvell.com,
coiby.xu@gmail.com, horms@kernel.org, brett.creeley@amd.com,
sgoutham@marvell.com, lcherian@marvell.com, gakula@marvell.com,
jerinj@marvell.com, hkelam@marvell.com, sbhatta@marvell.com,
idosch@nvidia.com, petrm@nvidia.com, eranbe@nvidia.com,
ayal@mellanox.com, leon@kernel.org, linux-kernel@vger.kernel.org,
bpoirier@suse.com
Subject: Re: [PATCH net-next v3 00/11] devlink: retain error in struct devlink_fmsg
Date: Fri, 20 Oct 2023 10:40:24 +0000 [thread overview]
Message-ID: <169779842464.30774.4987417905807311634.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231018202647.44769-1-przemyslaw.kitszel@intel.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 18 Oct 2023 22:26:36 +0200 you wrote:
> Extend devlink fmsg to retain error (patch 1),
> so drivers could omit error checks after devlink_fmsg_*() (patches 2-10),
> and finally enforce future uses to follow this practice by change to
> return void (patch 11)
>
> Note that it was compile tested only.
>
> [...]
Here is the summary with links:
- [net-next,v3,01/11] devlink: retain error in struct devlink_fmsg
(no matching commit)
- [net-next,v3,02/11] netdevsim: devlink health: use retained error fmsg API
(no matching commit)
- [net-next,v3,03/11] pds_core: devlink health: use retained error fmsg API
https://git.kernel.org/netdev/net-next/c/47957bb3f783
- [net-next,v3,04/11] bnxt_en: devlink health: use retained error fmsg API
(no matching commit)
- [net-next,v3,05/11] hinic: devlink health: use retained error fmsg API
(no matching commit)
- [net-next,v3,06/11] octeontx2-af: devlink health: use retained error fmsg API
https://git.kernel.org/netdev/net-next/c/d8cf03fca341
- [net-next,v3,07/11] mlxsw: core: devlink health: use retained error fmsg API
https://git.kernel.org/netdev/net-next/c/1d434b48495d
- [net-next,v3,08/11] net/mlx5: devlink health: use retained error fmsg API
(no matching commit)
- [net-next,v3,09/11] qed: devlink health: use retained error fmsg API
https://git.kernel.org/netdev/net-next/c/18256cb2d4a0
- [net-next,v3,10/11] staging: qlge: devlink health: use retained error fmsg API
https://git.kernel.org/netdev/net-next/c/3465915e9985
- [net-next,v3,11/11] devlink: convert most of devlink_fmsg_*() to return void
(no matching commit)
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:[~2023-10-20 10:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 20:26 [PATCH net-next v3 00/11] devlink: retain error in struct devlink_fmsg Przemek Kitszel
2023-10-18 20:26 ` [PATCH net-next v3 01/11] " Przemek Kitszel
2023-10-19 13:00 ` Simon Horman
2023-10-19 21:49 ` Przemek Kitszel
2023-10-18 20:26 ` [PATCH net-next v3 02/11] netdevsim: devlink health: use retained error fmsg API Przemek Kitszel
2023-10-19 15:56 ` Simon Horman
2023-10-18 20:26 ` [PATCH net-next v3 03/11] pds_core: " Przemek Kitszel
2023-10-19 15:56 ` Simon Horman
2023-10-18 20:26 ` [PATCH net-next v3 04/11] bnxt_en: " Przemek Kitszel
2023-10-19 15:56 ` Simon Horman
2023-10-18 20:26 ` [PATCH net-next v3 05/11] hinic: " Przemek Kitszel
2023-10-19 15:57 ` Simon Horman
2023-10-18 20:26 ` [PATCH net-next v3 06/11] octeontx2-af: " Przemek Kitszel
2023-10-19 15:57 ` Simon Horman
2023-10-18 20:26 ` [PATCH net-next v3 07/11] mlxsw: core: " Przemek Kitszel
2023-10-19 15:57 ` Simon Horman
2023-10-18 20:26 ` [PATCH net-next v3 08/11] net/mlx5: " Przemek Kitszel
2023-10-19 15:58 ` Simon Horman
2023-10-24 9:50 ` Dan Carpenter
2023-10-24 13:43 ` Przemek Kitszel
2023-10-18 20:26 ` [PATCH net-next v3 09/11] qed: " Przemek Kitszel
2023-10-19 15:58 ` Simon Horman
2023-10-18 20:26 ` [PATCH net-next v3 10/11] staging: qlge: " Przemek Kitszel
2023-10-19 15:58 ` Simon Horman
2023-10-18 20:26 ` [PATCH net-next v3 11/11] devlink: convert most of devlink_fmsg_*() to return void Przemek Kitszel
2023-10-19 13:44 ` [PATCH net-next v3 00/11] devlink: retain error in struct devlink_fmsg Jiri Pirko
2023-10-19 21:50 ` Przemek Kitszel
2023-10-20 9:36 ` Jiri Pirko
2023-10-20 10:40 ` 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=169779842464.30774.4987417905807311634.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aelior@marvell.com \
--cc=ayal@mellanox.com \
--cc=bpoirier@suse.com \
--cc=brett.creeley@amd.com \
--cc=cai.huoqing@linux.dev \
--cc=coiby.xu@gmail.com \
--cc=danieller@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eranbe@nvidia.com \
--cc=gakula@marvell.com \
--cc=george.cherian@marvell.com \
--cc=hkelam@marvell.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=irusskikh@marvell.com \
--cc=jerinj@marvell.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manishc@marvell.com \
--cc=michael.chan@broadcom.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=saeedm@nvidia.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=shannon.nelson@amd.com \
/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.