From: patchwork-bot+netdevbpf@kernel.org
To: Frank <Frank.Sae@motor-comm.com>
Cc: pgwipeout@gmail.com, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
yinghong.zhang@motor-comm.com, fei.zhang@motor-comm.com,
hua.sun@motor-comm.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: phy: add Motorcomm YT8531S phy id.
Date: Fri, 25 Nov 2022 08:10:16 +0000 [thread overview]
Message-ID: <166936381606.2494.8260000718729755967.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221122084232.3886-1-Frank.Sae@motor-comm.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 22 Nov 2022 16:42:32 +0800 you wrote:
> We added patch for motorcomm.c to support YT8531S. This patch has
> been tested on AM335x platform which has one YT8531S interface
> card and passed all test cases.
> The tested cases indluding: YT8531S UTP function with support of
> 10M/100M/1000M; YT8531S Fiber function with support of 100M/1000M;
> and YT8531S Combo function that supports auto detection of media type.
>
> [...]
Here is the summary with links:
- [net-next,v2] net: phy: add Motorcomm YT8531S phy id.
https://git.kernel.org/netdev/net-next/c/813abcd98fb1
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-11-25 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 8:42 [PATCH net-next v2] net: phy: add Motorcomm YT8531S phy id Frank
2022-11-25 8:10 ` 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=166936381606.2494.8260000718729755967.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Frank.Sae@motor-comm.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fei.zhang@motor-comm.com \
--cc=hkallweit1@gmail.com \
--cc=hua.sun@motor-comm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pgwipeout@gmail.com \
--cc=yinghong.zhang@motor-comm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox