public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Gatis Peisenieks <gatis@mikrotik.com>
Cc: chris.snook@gmail.com, davem@davemloft.net, kuba@kernel.org,
	hkallweit1@gmail.com, jesse.brandeburg@intel.com,
	dchickles@marvell.com, tully@mikrotik.com,
	eric.dumazet@gmail.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/5] atl1c: support for Mikrotik 10/25G NIC features
Date: Thu, 13 May 2021 22:50:12 +0000	[thread overview]
Message-ID: <162094621209.964.2203616230195452447.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210513114326.699663-1-gatis@mikrotik.com>

Hello:

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

On Thu, 13 May 2021 14:43:21 +0300 you wrote:
> The new Mikrotik 10/25G NIC maintains compatibility with existing atl1c
> driver. However it does have new features.
> 
> This patch set adds support for reporting cards higher link speed, max-mtu,
> enables rx csum offload and improves tx performance.
> 
> v2:
>     - fixed xmit_more handling as pointed out by Eric Dumazet
>     - added a more reliable link detection on Mikrotik 10/25G NIC
>       since MDIO op emulation can occasionally fail
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/5] atl1c: show correct link speed on Mikrotik 10/25G NIC
    https://git.kernel.org/netdev/net-next/c/f19d4997fd1f
  - [net-next,v2,2/5] atl1c: improve performance by avoiding unnecessary pcie writes on xmit
    https://git.kernel.org/netdev/net-next/c/d7ab6419bdee
  - [net-next,v2,3/5] atl1c: adjust max mtu according to Mikrotik 10/25G NIC ability
    https://git.kernel.org/netdev/net-next/c/545fa3fb1e84
  - [net-next,v2,4/5] atl1c: enable rx csum offload on Mikrotik 10/25G NIC
    https://git.kernel.org/netdev/net-next/c/b0390009502b
  - [net-next,v2,5/5] atl1c: improve link detection reliability on Mikrotik 10/25G NIC
    https://git.kernel.org/netdev/net-next/c/ea0fbd05d7bd

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-05-13 22:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-13 11:43 [PATCH net-next v2 0/5] atl1c: support for Mikrotik 10/25G NIC features Gatis Peisenieks
2021-05-13 11:43 ` [PATCH net-next v2 1/5] atl1c: show correct link speed on Mikrotik 10/25G NIC Gatis Peisenieks
2021-05-13 11:43 ` [PATCH net-next v2 2/5] atl1c: improve performance by avoiding unnecessary pcie writes on xmit Gatis Peisenieks
2021-05-13 11:43 ` [PATCH net-next v2 3/5] atl1c: adjust max mtu according to Mikrotik 10/25G NIC ability Gatis Peisenieks
2021-05-13 11:43 ` [PATCH net-next v2 4/5] atl1c: enable rx csum offload on Mikrotik 10/25G NIC Gatis Peisenieks
2021-05-13 11:43 ` [PATCH net-next v2 5/5] atl1c: improve link detection reliability " Gatis Peisenieks
2021-05-13 22: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=162094621209.964.2203616230195452447.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=chris.snook@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dchickles@marvell.com \
    --cc=eric.dumazet@gmail.com \
    --cc=gatis@mikrotik.com \
    --cc=hkallweit1@gmail.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tully@mikrotik.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