All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Marek_Beh=C3=BAn_=3Ckabel=40kernel=2Eorg=3E?=@ci.codeaurora.org
Cc: netdev@vger.kernel.org, rmk+kernel@armlinux.org.uk,
	kuba@kernel.org, andrew@lunn.ch, davem@davemloft.net
Subject: Re: [PATCH net-next 0/2] Add 5gbase-r support for mvpp2
Date: Tue, 23 Nov 2021 12:20:12 +0000	[thread overview]
Message-ID: <163767001202.10565.9680629278046876801.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211122205111.10156-1-kabel@kernel.org>

Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Mon, 22 Nov 2021 21:51:09 +0100 you wrote:
> Hello,
> 
> this adds support for 5gbase-r for mvpp2 driver. Current versions of
> TF-A firmware support changing the PHY to 5gbase-r via SMC calls, at
> least on Macchiatobin.
> 
> Tested on Macchiatobin.
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] phy: marvell: phy-mvebu-cp110-comphy: add support for 5gbase-r
    https://git.kernel.org/netdev/net-next/c/a1fb410a5751
  - [net-next,2/2] net: marvell: mvpp2: Add support for 5gbase-r
    https://git.kernel.org/netdev/net-next/c/4043ec701c43

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-11-23 12:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 20:51 [PATCH net-next 0/2] Add 5gbase-r support for mvpp2 Marek Behún
2021-11-22 20:51 ` [PATCH net-next 1/2] phy: marvell: phy-mvebu-cp110-comphy: add support for 5gbase-r Marek Behún
2021-11-22 20:51 ` [PATCH net-next 2/2] net: marvell: mvpp2: Add " Marek Behún
2021-11-23 12:20 ` 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=163767001202.10565.9680629278046876801.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc==?utf-8?q?Marek_Beh=C3=BAn_=3Ckabel=40kernel=2Eorg=3E?=@ci.codeaurora.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rmk+kernel@armlinux.org.uk \
    /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.