Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: s.shtylyov@omp.ru, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, lanhao@huawei.com,
	simon.horman@corigine.com, netdev@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org, phong.hoang.wz@renesas.com
Subject: Re: [PATCH net v3] net: renesas: rswitch: Fix timestamp feature after all descriptors are used
Date: Fri, 09 Jun 2023 09:50:21 +0000	[thread overview]
Message-ID: <168630422139.21394.17316227658031207308.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230608015727.1862917-1-yoshihiro.shimoda.uh@renesas.com>

Hello:

This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:

On Thu,  8 Jun 2023 10:57:27 +0900 you wrote:
> The timestamp descriptors were intended to act cyclically. Descriptors
> from index 0 through gq->ring_size - 1 contain actual information, and
> the last index (gq->ring_size) should have LINKFIX to indicate
> the first index 0 descriptor. However, the LINKFIX value is missing,
> causing the timestamp feature to stop after all descriptors are used.
> To resolve this issue, set the LINKFIX to the timestamp descritors.
> 
> [...]

Here is the summary with links:
  - [net,v3] net: renesas: rswitch: Fix timestamp feature after all descriptors are used
    https://git.kernel.org/netdev/net/c/0ad4982c520e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-06-09  9:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08  1:57 [PATCH net v3] net: renesas: rswitch: Fix timestamp feature after all descriptors are used Yoshihiro Shimoda
2023-06-08 13:51 ` Simon Horman
2023-06-09  9:50 ` 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=168630422139.21394.17316227658031207308.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=lanhao@huawei.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=phong.hoang.wz@renesas.com \
    --cc=s.shtylyov@omp.ru \
    --cc=simon.horman@corigine.com \
    --cc=yoshihiro.shimoda.uh@renesas.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