From: patchwork-bot+netdevbpf@kernel.org
To: Rakesh Babu Saladi <rsaladi2@marvell.com>
Cc: sgoutham@marvell.com, gakula@marvell.com, sbhatta@marvell.com,
hkelam@marvell.com, davem@davemloft.net, kuba@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
richardcochran@gmail.com
Subject: Re: [net-next PATCH v2 0/2] RVU AF and NETDEV drivers' PTP updates.
Date: Mon, 21 Feb 2022 13:10:09 +0000 [thread overview]
Message-ID: <164544900985.23760.15653354946520544563.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220221064508.19148-1-rsaladi2@marvell.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 21 Feb 2022 12:15:06 +0530 you wrote:
> Patch 1: Add suppot such that RVU drivers support new timestamp format.
> Patch 2: This patch adds workaround for PTP errata.
>
> Changes made from v1 to v2
> 1. CC'd Richard Cochran to review PTP related patches.
> 2. Removed a patch from the old patch series. Will submit the removed patch
> separately.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] octeontx2-pf: cn10k: add support for new ptp timestamp format
https://git.kernel.org/netdev/net-next/c/74c1b2338e0e
- [net-next,v2,2/2] octeontx2-af: cn10k: add workaround for ptp errata
https://git.kernel.org/netdev/net-next/c/6426fc3abab9
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-02-21 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 6:45 [net-next PATCH v2 0/2] RVU AF and NETDEV drivers' PTP updates Rakesh Babu Saladi
2022-02-21 6:45 ` [net-next PATCH v2 1/2] octeontx2-pf: cn10k: add support for new ptp timestamp format Rakesh Babu Saladi
2022-02-21 6:45 ` [net-next PATCH v2 2/2] octeontx2-af: cn10k: add workaround for ptp errata Rakesh Babu Saladi
2022-02-21 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=164544900985.23760.15653354946520544563.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=rsaladi2@marvell.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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.