All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
	andrew+netdev@lunn.ch, daniel@iogearbox.net, willemb@google.com
Subject: Re: [PATCH net] net/packet: ignore timestamp bits when testing tx frame status
Date: Wed, 07 Oct 2026 00:50:09 +0000	[thread overview]
Message-ID: <179133420927.2847663.11266607663263644162.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261004171847.186954-1-willemdebruijn.kernel@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Sun,  4 Oct 2026 13:10:53 -0400 you wrote:
> From: Willem de Bruijn <willemb@google.com>
> 
> Since the commit in Fixes, the tx completion handler writes the frame
> status as TP_STATUS_AVAILABLE | ts, where ts can be
> TP_STATUS_TS_SOFTWARE or TP_STATUS_TS_RAW_HARDWARE.
> 
> Two places compare a tx frame status to TP_STATUS_AVAILABLE for
> equality, and so fail to detect such a released frame:
> 
> [...]

Here is the summary with links:
  - [net] net/packet: ignore timestamp bits when testing tx frame status
    https://git.kernel.org/netdev/net-next/c/88fb9fad5cbe

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



      parent reply	other threads:[~2026-10-07  0:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-04 17:10 [PATCH net] net/packet: ignore timestamp bits when testing tx frame status Willem de Bruijn
2026-10-04 17:24 ` netdev-bot+sinfo
2026-10-04 22:37   ` Willem de Bruijn
2026-10-07  0: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=179133420927.2847663.11266607663263644162.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemb@google.com \
    --cc=willemdebruijn.kernel@gmail.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.