Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, tariqt@nvidia.com,
	yishaih@nvidia.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next 0/4] mlx4: prep for constant dev->dev_addr
Date: Tue, 05 Oct 2021 12:30:07 +0000	[thread overview]
Message-ID: <163343700780.31035.7456152330471867151.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211004191446.2127522-1-kuba@kernel.org>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Mon,  4 Oct 2021 12:14:42 -0700 you wrote:
> This patch converts mlx4 for dev->dev_addr being const. It converts
> to use of common helpers but also removes some seemingly unnecessary
> idiosyncrasies.
> 
> Please review.
> 
> Jakub Kicinski (4):
>   mlx4: replace mlx4_mac_to_u64() with ether_addr_to_u64()
>   mlx4: replace mlx4_u64_to_mac() with u64_to_ether_addr()
>   mlx4: remove custom dev_addr clearing
>   mlx4: constify args for const dev_addr
> 
> [...]

Here is the summary with links:
  - [net-next,1/4] mlx4: replace mlx4_mac_to_u64() with ether_addr_to_u64()
    https://git.kernel.org/netdev/net-next/c/ded6e16b37e4
  - [net-next,2/4] mlx4: replace mlx4_u64_to_mac() with u64_to_ether_addr()
    https://git.kernel.org/netdev/net-next/c/1bb96a07f9a8
  - [net-next,3/4] mlx4: remove custom dev_addr clearing
    https://git.kernel.org/netdev/net-next/c/e04ffd120f3c
  - [net-next,4/4] mlx4: constify args for const dev_addr
    https://git.kernel.org/netdev/net-next/c/ebb1fdb589bd

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



      parent reply	other threads:[~2021-10-05 12:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04 19:14 [PATCH net-next 0/4] mlx4: prep for constant dev->dev_addr Jakub Kicinski
2021-10-04 19:14 ` [PATCH net-next 1/4] mlx4: replace mlx4_mac_to_u64() with ether_addr_to_u64() Jakub Kicinski
2021-10-05  9:55   ` Tariq Toukan
2021-10-04 19:14 ` [PATCH net-next 2/4] mlx4: replace mlx4_u64_to_mac() with u64_to_ether_addr() Jakub Kicinski
2021-10-05  9:59   ` Tariq Toukan
2021-10-04 19:14 ` [PATCH net-next 3/4] mlx4: remove custom dev_addr clearing Jakub Kicinski
2021-10-05 10:21   ` Tariq Toukan
2021-10-04 19:14 ` [PATCH net-next 4/4] mlx4: constify args for const dev_addr Jakub Kicinski
2021-10-05 10:27   ` Tariq Toukan
2021-10-05 10:28 ` [PATCH net-next 0/4] mlx4: prep for constant dev->dev_addr Tariq Toukan
2021-10-05 12: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=163343700780.31035.7456152330471867151.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tariqt@nvidia.com \
    --cc=yishaih@nvidia.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