Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [net-next,
 v2] enetc: fix locking for one-step timestamping packet transfer
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <161921161322.19917.12823767295470536369.git-patchwork-notify@kernel.org>
Date:   Fri, 23 Apr 2021 21:00:13 +0000
References: <20210423093355.8665-1-yangbo.lu@nxp.com>
In-Reply-To: <20210423093355.8665-1-yangbo.lu@nxp.com>
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
Precedence: bulk

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