From: patchwork-bot+netdevbpf@kernel.org
To: Jacob Keller <jacob.e.keller@intel.com>
Cc: netdev@vger.kernel.org, jiri@nvidia.com, kuba@kernel.org
Subject: Re: [PATCH net-next v3 0/9] support direct read from region
Date: Thu, 01 Dec 2022 05:50:17 +0000 [thread overview]
Message-ID: <166987381770.9213.13433605043891965239.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221128203647.1198669-1-jacob.e.keller@intel.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 28 Nov 2022 12:36:38 -0800 you wrote:
> Changes since v2:
> * Picked up ack/review tags
> * Added DEVLINK_ATTR_REGION_DIRECT so userspace must be explicit
> * Fixed the capitalization of netlink error messages
>
> Changes since v1:
> * Re-ordered patches at the beginning slightly, pulling min_t change and
> reporting of extended error messages to the start of the series.
> * use NL_SET_ERR_MSG_ATTR for reporting invalid attributes
> * Use kmalloc instead of kzalloc
> * Cleanup spacing around data_size
> * Fix the __always_unused positioning
> * Update documentation for direct reads to clearly explain they are not
> atomic for larger reads.
> * Add a patch to fix missing documentation for ice.rst
> * Mention the direct read support in ice.rst documentation
>
> [...]
Here is the summary with links:
- [net-next,v3,1/9] devlink: use min_t to calculate data_size
https://git.kernel.org/netdev/net-next/c/28e0c250f17a
- [net-next,v3,2/9] devlink: report extended error message in region_read_dumpit()
https://git.kernel.org/netdev/net-next/c/611fd12ce0fb
- [net-next,v3,3/9] devlink: find snapshot in devlink_nl_cmd_region_read_dumpit
https://git.kernel.org/netdev/net-next/c/e004ea10599d
- [net-next,v3,4/9] devlink: remove unnecessary parameter from chunk_fill function
https://git.kernel.org/netdev/net-next/c/284e9d1ebbe2
- [net-next,v3,5/9] devlink: refactor region_read_snapshot_fill to use a callback function
https://git.kernel.org/netdev/net-next/c/2d4caf0988bd
- [net-next,v3,6/9] devlink: support directly reading from region memory
https://git.kernel.org/netdev/net-next/c/af6397c9ee2b
- [net-next,v3,7/9] ice: use same function to snapshot both NVM and Shadow RAM
https://git.kernel.org/netdev/net-next/c/ed23debec5d1
- [net-next,v3,8/9] ice: document 'shadow-ram' devlink region
https://git.kernel.org/netdev/net-next/c/2d0197843f9e
- [net-next,v3,9/9] ice: implement direct read for NVM and Shadow RAM regions
https://git.kernel.org/netdev/net-next/c/3af4b40b0f2f
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:[~2022-12-01 5:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 20:36 [PATCH net-next v3 0/9] support direct read from region Jacob Keller
2022-11-28 20:36 ` [PATCH net-next v3 1/9] devlink: use min_t to calculate data_size Jacob Keller
2022-11-28 20:36 ` [PATCH net-next v3 2/9] devlink: report extended error message in region_read_dumpit() Jacob Keller
2022-11-28 20:36 ` [PATCH net-next v3 3/9] devlink: find snapshot in devlink_nl_cmd_region_read_dumpit Jacob Keller
2022-11-28 20:36 ` [PATCH net-next v3 4/9] devlink: remove unnecessary parameter from chunk_fill function Jacob Keller
2022-11-28 20:36 ` [PATCH net-next v3 5/9] devlink: refactor region_read_snapshot_fill to use a callback function Jacob Keller
2022-11-28 20:36 ` [PATCH net-next v3 6/9] devlink: support directly reading from region memory Jacob Keller
2022-11-29 8:17 ` Jiri Pirko
2022-11-28 20:36 ` [PATCH net-next v3 7/9] ice: use same function to snapshot both NVM and Shadow RAM Jacob Keller
2022-11-28 20:36 ` [PATCH net-next v3 8/9] ice: document 'shadow-ram' devlink region Jacob Keller
2022-11-28 20:36 ` [PATCH net-next v3 9/9] ice: implement direct read for NVM and Shadow RAM regions Jacob Keller
2022-12-01 5:50 ` 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=166987381770.9213.13433605043891965239.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.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.