From: patchwork-bot+netdevbpf@kernel•org
To: Yuiko Oshino <yuiko.oshino@microchip•com>
Cc: woojung.huh@microchip•com, davem@davemloft•net,
netdev@vger•kernel.org, andrew@lunn•ch, ravi.hegde@microchip•com,
UNGLinuxDriver@microchip•com, kuba@kernel•org
Subject: Re: [PATCH v4 net-next 0/2] net: phy: add LAN8742 phy support
Date: Mon, 09 May 2022 13:40:14 +0000 [thread overview]
Message-ID: <165210361423.30657.3972779184170370201.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220505181252.32196-1-yuiko.oshino@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft•net>:
On Thu, 5 May 2022 11:12:50 -0700 you wrote:
> add LAN8742 phy support
> update LAN88xx phy ID and phy ID mask so that it can coexist with LAN8742
>
> The current phy IDs on the available hardware.
> LAN8742 0x0007C130, 0x0007C131
> LAN88xx 0x0007C132
>
> [...]
Here is the summary with links:
- [v4,net-next,1/2] net: phy: microchip: update LAN88xx phy ID and phy ID mask.
https://git.kernel.org/netdev/net-next/c/e078286a1375
- [v4,net-next,2/2] net: phy: smsc: add LAN8742 phy support.
https://git.kernel.org/netdev/net-next/c/53ad22868289
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-05-09 13:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 18:12 [PATCH v4 net-next 0/2] net: phy: add LAN8742 phy support Yuiko Oshino
2022-05-05 18:12 ` [PATCH v4 net-next 1/2] net: phy: microchip: update LAN88xx phy ID and phy ID mask Yuiko Oshino
2022-05-05 18:12 ` [PATCH v4 net-next 2/2] net: phy: smsc: add LAN8742 phy support Yuiko Oshino
2022-05-05 19:29 ` Andrew Lunn
2022-05-06 22:45 ` Jakub Kicinski
2022-05-07 13:48 ` Andrew Lunn
2022-05-09 13:47 ` Yuiko.Oshino
2022-05-09 13:50 ` Andrew Lunn
2022-05-09 14:24 ` Yuiko.Oshino
2022-05-09 16:35 ` Jakub Kicinski
2022-05-09 11:45 ` Yuiko.Oshino
2022-05-09 13: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=165210361423.30657.3972779184170370201.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=UNGLinuxDriver@microchip$(echo .)com \
--cc=andrew@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=ravi.hegde@microchip$(echo .)com \
--cc=woojung.huh@microchip$(echo .)com \
--cc=yuiko.oshino@microchip$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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