From: patchwork-bot+netdevbpf@kernel.org
To: Yuji Ishikawa <yuji2.ishikawa@toshiba.co.jp>
Cc: davem@davemloft.net, kuba@kernel.org, peppe.cavallaro@st.com,
alexandre.torgue@st.com, joabreu@synopsys.com,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, nobuhiro1.iwamatsu@toshiba.co.jp
Subject: Re: [PATCH 0/1] net: stmmac: dwmac-visconti: Avoid updating hardware register for unexpected speed requst
Date: Fri, 28 Jan 2022 14:30:10 +0000 [thread overview]
Message-ID: <164338021033.15816.13738860195654864475.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220127121714.22915-1-yuji2.ishikawa@toshiba.co.jp>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 27 Jan 2022 21:17:13 +0900 you wrote:
> Function visconti_eth_fix_mac_speed() should not change a register when an unexpected speed value is passed.
>
> Yuji Ishikawa (1):
> net: stmmac: dwmac-visconti: No change to ETHER_CLOCK_SEL for
> unexpected speed request.
>
> drivers/net/ethernet/stmicro/stmmac/dwmac-visconti.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
Here is the summary with links:
- [1/1] net: stmmac: dwmac-visconti: No change to ETHER_CLOCK_SEL for unexpected speed request.
https://git.kernel.org/netdev/net/c/928d6fe996f6
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-01-28 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 12:17 Yuji Ishikawa
2022-01-27 12:17 ` [PATCH 1/1] net: stmmac: dwmac-visconti: No change to ETHER_CLOCK_SEL for unexpected speed request Yuji Ishikawa
2022-01-28 14:30 ` 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=164338021033.15816.13738860195654864475.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=davem@davemloft.net \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=peppe.cavallaro@st.com \
--cc=yuji2.ishikawa@toshiba.co.jp \
/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
Powered by JetHome