From: patchwork-bot+netdevbpf@kernel.org
To: Yangbo Lu <yangbo.lu@nxp.com>
Cc: netdev@vger.kernel.org, richardcochran@gmail.com,
vladimir.oltean@nxp.com, davem@davemloft.net, kuba@kernel.org,
claudiu.manoil@nxp.com, linux-kernel@vger.kernel.org
Subject: Re: [net-next, v2] enetc: fix locking for one-step timestamping packet transfer
Date: Fri, 23 Apr 2021 21:00:13 +0000 [thread overview]
Message-ID: <161921161322.19917.12823767295470536369.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210423093355.8665-1-yangbo.lu@nxp.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Fri, 23 Apr 2021 17:33:55 +0800 you wrote:
> The previous patch to support PTP Sync packet one-step timestamping
> described one-step timestamping packet handling logic as below in
> commit message:
>
> - Trasmit packet immediately if no other one in transfer, or queue to
> skb queue if there is already one in transfer.
> The test_and_set_bit_lock() is used here to lock and check state.
> - Start a work when complete transfer on hardware, to release the bit
> lock and to send one skb in skb queue if has.
>
> [...]
Here is the summary with links:
- [net-next,v2] enetc: fix locking for one-step timestamping packet transfer
https://git.kernel.org/netdev/net-next/c/7ce9c3d363ac
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-04-23 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 9:33 [net-next, v2] enetc: fix locking for one-step timestamping packet transfer Yangbo Lu
2021-04-23 21:00 ` 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=161921161322.19917.12823767295470536369.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=vladimir.oltean@nxp.com \
--cc=yangbo.lu@nxp.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 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).