From: patchwork-bot+netdevbpf@kernel.org
To: <ecree@xilinx.com>
Cc: netdev@vger.kernel.org, linux-net-drivers@amd.com,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, corbet@lwn.net, linux-doc@vger.kernel.org,
jacob.e.keller@intel.com, jesse.brandeburg@intel.com,
michael.chan@broadcom.com, andy@greyhouse.net, saeed@kernel.org,
jiri@resnulli.us, snelson@pensando.io, simon.horman@corigine.com,
alexander.duyck@gmail.com, rdunlap@infradead.org,
parav@nvidia.com, roid@nvidia.com, marcin.szycik@linux.intel.com,
ecree.xilinx@gmail.com
Subject: Re: [PATCH v3 net-next] docs: net: add an explanation of VF (and other) Representors
Date: Wed, 21 Sep 2022 14:40:15 +0000 [thread overview]
Message-ID: <166377121530.12143.786016178695125042.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220905135557.39233-1-ecree@xilinx.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 5 Sep 2022 14:55:57 +0100 you wrote:
> From: Edward Cree <ecree.xilinx@gmail.com>
>
> There's no clear explanation of what VF Representors are for, their
> semantics, etc., outside of vendor docs and random conference slides.
> Add a document explaining Representors and defining what drivers that
> implement them are expected to do.
>
> [...]
Here is the summary with links:
- [v3,net-next] docs: net: add an explanation of VF (and other) Representors
https://git.kernel.org/netdev/net-next/c/6fb4825e492b
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-09-21 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 13:55 [PATCH v3 net-next] docs: net: add an explanation of VF (and other) Representors ecree
2022-09-06 9:29 ` Bagas Sanjaya
2022-09-20 12:40 ` Edward Cree
2022-09-20 13:08 ` Jonathan Corbet
2022-09-21 14: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=166377121530.12143.786016178695125042.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexander.duyck@gmail.com \
--cc=andy@greyhouse.net \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=ecree@xilinx.com \
--cc=edumazet@google.com \
--cc=jacob.e.keller@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=marcin.szycik@linux.intel.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=rdunlap@infradead.org \
--cc=roid@nvidia.com \
--cc=saeed@kernel.org \
--cc=simon.horman@corigine.com \
--cc=snelson@pensando.io \
/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;
as well as URLs for NNTP newsgroup(s).