All of lore.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,
	richardcochran@gmail.com, jacob.e.keller@intel.com
Subject: Re: [PATCH net-next 0/7][pull request] 1GbE Intel Wired LAN Driver Updates 2022-07-28
Date: Mon, 01 Aug 2022 18:30:14 +0000	[thread overview]
Message-ID: <165937861431.31008.6507520694277325694.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220728181836.3387862-1-anthony.l.nguyen@intel.com>

Hello:

This series was applied to netdev/net-next.git (master)
by Tony Nguyen <anthony.l.nguyen@intel.com>:

On Thu, 28 Jul 2022 11:18:29 -0700 you wrote:
> Jacob Keller says:
> 
> Convert all of the Intel drivers with PTP support to the newer .adjfine
> implementation which uses scaled parts per million.
> 
> This improves the precision of the frequency adjustments by taking advantage
> of the full scaled parts per million input coming from user space.
> 
> [...]

Here is the summary with links:
  - [net-next,1/7] ice: implement adjfine with mul_u64_u64_div_u64
    https://git.kernel.org/netdev/net-next/c/4488df140152
  - [net-next,2/7] e1000e: remove unnecessary range check in e1000e_phc_adjfreq
    https://git.kernel.org/netdev/net-next/c/ab8e8db27e82
  - [net-next,3/7] e1000e: convert .adjfreq to .adjfine
    https://git.kernel.org/netdev/net-next/c/abab010f1637
  - [net-next,4/7] i40e: use mul_u64_u64_div_u64 for PTP frequency calculation
    https://git.kernel.org/netdev/net-next/c/3626a690b717
  - [net-next,5/7] i40e: convert .adjfreq to .adjfine
    https://git.kernel.org/netdev/net-next/c/ccd3bf985921
  - [net-next,6/7] ixgbe: convert .adjfreq to .adjfine
    https://git.kernel.org/netdev/net-next/c/5a5542324a4a
  - [net-next,7/7] igb: convert .adjfreq to .adjfine
    https://git.kernel.org/netdev/net-next/c/d8fae2504efe

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



      parent reply	other threads:[~2022-08-01 18:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28 18:18 [PATCH net-next 0/7][pull request] 1GbE Intel Wired LAN Driver Updates 2022-07-28 Tony Nguyen
2022-07-28 18:18 ` [PATCH net-next 1/7] ice: implement adjfine with mul_u64_u64_div_u64 Tony Nguyen
2022-07-28 18:18 ` [PATCH net-next 2/7] e1000e: remove unnecessary range check in e1000e_phc_adjfreq Tony Nguyen
2022-07-28 18:18 ` [PATCH net-next 3/7] e1000e: convert .adjfreq to .adjfine Tony Nguyen
2022-07-28 18:18 ` [PATCH net-next 4/7] i40e: use mul_u64_u64_div_u64 for PTP frequency calculation Tony Nguyen
2022-07-28 18:18 ` [PATCH net-next 5/7] i40e: convert .adjfreq to .adjfine Tony Nguyen
2022-07-28 18:18 ` [PATCH net-next 6/7] ixgbe: " Tony Nguyen
2022-07-28 18:18 ` [PATCH net-next 7/7] igb: " Tony Nguyen
2022-08-01 16:56 ` [PATCH net-next 0/7][pull request] 1GbE Intel Wired LAN Driver Updates 2022-07-28 Tony Nguyen
2022-08-01 17:22   ` Jakub Kicinski
2022-08-01 18:30 ` 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=165937861431.31008.6507520694277325694.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jacob.e.keller@intel.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=richardcochran@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.