netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andre Edich <andre.edich@microchip.com>
Cc: netdev@vger.kernel.org, UNGLinuxDriver@microchip.com,
	Parthiban.Veerasooran@microchip.com, mans@mansr.com
Subject: Re: [PATCH net-next] net: phy: lan87xx: fix access to wrong register of LAN87xx
Date: Tue, 30 Mar 2021 20:20:09 +0000	[thread overview]
Message-ID: <161713560918.2790.13371551221306898976.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210329094536.3118619-1-andre.edich@microchip.com>

Hello:

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

On Mon, 29 Mar 2021 11:45:36 +0200 you wrote:
> The function lan87xx_config_aneg_ext was introduced to configure
> LAN95xxA but as well writes to undocumented register of LAN87xx.
> This fix prevents that access.
> 
> The function lan87xx_config_aneg_ext gets more suitable for the new
> behavior name.
> 
> [...]

Here is the summary with links:
  - [net-next] net: phy: lan87xx: fix access to wrong register of LAN87xx
    https://git.kernel.org/netdev/net-next/c/fdb5cc6ab3b6

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-03-30 20:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29  9:45 [PATCH net-next] net: phy: lan87xx: fix access to wrong register of LAN87xx Andre Edich
2021-03-29 11:19 ` Måns Rullgård
2021-03-29 12:07   ` Andre.Edich
2021-03-29 17:40     ` Måns Rullgård
2021-03-30 12:01 ` Måns Rullgård
2021-03-30 20: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=161713560918.2790.13371551221306898976.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Parthiban.Veerasooran@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andre.edich@microchip.com \
    --cc=mans@mansr.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).