All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <linux@armlinux.org.uk>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, clabbe.montjoie@gmail.com,
	davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] Fix RGMII delays for 88E1118
Date: Wed, 05 Jan 2022 18:40:09 +0000	[thread overview]
Message-ID: <164140800987.26997.5157711967698870664.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <YdR3wYFkm4eJApwb@shell.armlinux.org.uk>

Hello:

This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 4 Jan 2022 16:37:21 +0000 you wrote:
> Hi,
> 
> This series fixes the RGMII delays for 88E1118 Marvell PHYs, after a
> report by Corentin Labbe that the Marvell driver fails to work.
> 
> Patch 1 cleans up the paged register accesses in m88e1118_config_init()
> and patch 2 adds the RGMII delay configuration.
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] net: phy: marvell: use phy_write_paged() to set MSCR
    https://git.kernel.org/netdev/net-next/c/5b8f970309dd
  - [net-next,2/2] net: phy: marvell: configure RGMII delays for 88E1118
    https://git.kernel.org/netdev/net-next/c/f22725c95ece

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-01-05 18:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 16:37 [PATCH net-next 0/2] Fix RGMII delays for 88E1118 Russell King (Oracle)
2022-01-04 16:38 ` [PATCH net-next 1/2] net: phy: marvell: use phy_write_paged() to set MSCR Russell King (Oracle)
2022-01-04 16:44   ` Andrew Lunn
2022-01-04 19:53   ` Corentin Labbe
2022-01-04 16:38 ` [PATCH net-next 2/2] net: phy: marvell: configure RGMII delays for 88E1118 Russell King (Oracle)
2022-01-04 16:45   ` Andrew Lunn
2022-01-05 18:40 ` 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=164140800987.26997.5157711967698870664.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=clabbe.montjoie@gmail.com \
    --cc=davem@davemloft.net \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    /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.