From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?Q2zDqW1lbnQgTMOpZ2VyIDxjbGVtZW50LmxlZ2VyQGJvb3RsaW4uY29tPg==?=@ci.codeaurora.org
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux-renesas-soc@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@bootlin.com, herve.codina@bootlin.com,
miquel.raynal@bootlin.com, milan.stevanovic@se.com,
jimmy.lalande@se.com, pascal.eberhard@se.com
Subject: Re: [PATCH net-next] net: pcs: rzn1-miic: update speed only if interface is changed
Date: Sat, 02 Jul 2022 03:20:15 +0000 [thread overview]
Message-ID: <165673201545.6297.13593698889727547584.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220629122003.189397-1-clement.leger@bootlin.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 29 Jun 2022 14:20:03 +0200 you wrote:
> As stated by Russel King, miic_config() can be called as a result of
> ethtool setting the configuration while the link is already up. Since
> the speed is also set in this function, it could potentially modify
> the current speed that is set. This will only happen if there is
> no PHY present and we aren't using fixed-link mode.
>
> Handle that by storing the current interface mode in the miic_port
> structure and update the speed only if the interface mode is going to
> be changed.
>
> [...]
Here is the summary with links:
- [net-next] net: pcs: rzn1-miic: update speed only if interface is changed
https://git.kernel.org/netdev/net-next/c/90c74f4d90ad
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-07-02 3:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 12:20 [PATCH net-next] net: pcs: rzn1-miic: update speed only if interface is changed Clément Léger
2022-07-02 3: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=165673201545.6297.13593698889727547584.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?Q2zDqW1lbnQgTMOpZ2VyIDxjbGVtZW50LmxlZ2VyQGJvb3RsaW4uY29tPg==?=@ci.codeaurora.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herve.codina@bootlin.com \
--cc=hkallweit1@gmail.com \
--cc=jimmy.lalande@se.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=milan.stevanovic@se.com \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pascal.eberhard@se.com \
--cc=thomas.petazzoni@bootlin.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 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.