public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Tony Nguyen <anthony.l.nguyen@intel•com>
Cc: davem@davemloft•net, kuba@kernel•org, pabeni@redhat•com,
	edumazet@google•com, netdev@vger•kernel.org,
	vadim.fedorenko@linux•dev, richardcochran@gmail•com,
	horms@kernel•org, himasekharx.reddy.pucha@intel•com
Subject: Re: [PATCH net] ixgbe: fix timestamp configuration code
Date: Wed, 13 Sep 2023 11:30:26 +0000	[thread overview]
Message-ID: <169460462626.4298.16639828880343505002.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230911202814.147456-1-anthony.l.nguyen@intel.com>

Hello:

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

On Mon, 11 Sep 2023 13:28:14 -0700 you wrote:
> From: Vadim Fedorenko <vadim.fedorenko@linux•dev>
> 
> The commit in fixes introduced flags to control the status of hardware
> configuration while processing packets. At the same time another structure
> is used to provide configuration of timestamper to user-space applications.
> The way it was coded makes this structures go out of sync easily. The
> repro is easy for 82599 chips:
> 
> [...]

Here is the summary with links:
  - [net] ixgbe: fix timestamp configuration code
    https://git.kernel.org/netdev/net/c/3c44191dd76c

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



  reply	other threads:[~2023-09-13 11:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11 20:28 [PATCH net] ixgbe: fix timestamp configuration code Tony Nguyen
2023-09-13 11:30 ` patchwork-bot+netdevbpf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-23 22:15 Vadim Fedorenko
2023-08-24 14:49 ` Simon Horman

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=169460462626.4298.16639828880343505002.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=anthony.l.nguyen@intel$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=himasekharx.reddy.pucha@intel$(echo .)com \
    --cc=horms@kernel$(echo .)org \
    --cc=kuba@kernel$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=richardcochran@gmail$(echo .)com \
    --cc=vadim.fedorenko@linux$(echo .)dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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