From: patchwork-bot+netdevbpf@kernel•org
To: Subbaraya Sundeep <sbhatta@marvell•com>
Cc: davem@davemloft•net, kuba@kernel•org, netdev@vger•kernel.org,
sgoutham@marvell•com, hkelam@marvell•com, gakula@marvell•com,
naveenm@marvell•com, rsaladi2@marvell•com
Subject: Re: [net-next PATCH 0/2] Add PTP support for VFs
Date: Wed, 29 Sep 2021 09:40:08 +0000 [thread overview]
Message-ID: <163290840847.357.9087499209887090868.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1632851026-5415-1-git-send-email-sbhatta@marvell.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Tue, 28 Sep 2021 23:13:44 +0530 you wrote:
> PTP is a shared hardware block which can prepend
> RX timestamps to packets before directing packets to
> PFs or VFs and can notify the TX timestamps to PFs or VFs
> via TX completion queue descriptors. Hence adding PTP
> support for VFs is exactly similar to PFs with minimal changes.
> This patchset adds that PTP support for VFs.
>
> [...]
Here is the summary with links:
- [net-next,1/2] octeontx2-pf: Enable promisc/allmulti match MCAM entries.
https://git.kernel.org/netdev/net-next/c/ffd2f89ad05c
- [net-next,2/2] octeontx2-nicvf: Add PTP hardware clock support to NIX VF
https://git.kernel.org/netdev/net-next/c/43510ef4ddad
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-09-29 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 17:43 [net-next PATCH 0/2] Add PTP support for VFs Subbaraya Sundeep
2021-09-28 17:43 ` [net-next PATCH 1/2] octeontx2-pf: Enable promisc/allmulti match MCAM entries Subbaraya Sundeep
2021-09-28 17:43 ` [net-next PATCH 2/2] octeontx2-nicvf: Add PTP hardware clock support to NIX VF Subbaraya Sundeep
2021-09-29 9: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=163290840847.357.9087499209887090868.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=gakula@marvell$(echo .)com \
--cc=hkelam@marvell$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=naveenm@marvell$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=rsaladi2@marvell$(echo .)com \
--cc=sbhatta@marvell$(echo .)com \
--cc=sgoutham@marvell$(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