From: patchwork-bot+netdevbpf@kernel.org
To: Duanqiang Wen <duanqiangwen@net-swift.com>
Cc: netdev@vger.kernel.org, jiawenwu@trustnetic.com,
mengyuanlou@net-swift.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
maciej.fijalkowski@intel.com, andrew@lunn.ch
Subject: Re: [PATCH net 1/2] Revert "net: txgbe: fix i2c dev name cannot match clkdev"
Date: Thu, 25 Apr 2024 03:00:28 +0000 [thread overview]
Message-ID: <171401402832.32160.14071159006302877526.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240422084109.3201-1-duanqiangwen@net-swift.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 22 Apr 2024 16:41:08 +0800 you wrote:
> This reverts commit c644920ce9220d83e070f575a4df711741c07f07.
> when register i2c dev, txgbe shorten "i2c_designware" to "i2c_dw",
> will cause this i2c dev can't match platfom driver i2c_designware_platform.
>
> Signed-off-by: Duanqiang Wen <duanqiangwen@net-swift.com>
> ---
> drivers/net/ethernet/wangxun/txgbe/txgbe_phy.c | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
Here is the summary with links:
- [net,1/2] Revert "net: txgbe: fix i2c dev name cannot match clkdev"
https://git.kernel.org/netdev/net/c/8d6bf83f6740
- [net,2/2] Revert "net: txgbe: fix clk_name exceed MAX_DEV_ID limits"
https://git.kernel.org/netdev/net/c/edd2d250fb3b
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:[~2024-04-25 3:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 8:41 [PATCH net 1/2] Revert "net: txgbe: fix i2c dev name cannot match clkdev" Duanqiang Wen
2024-04-22 8:41 ` [PATCH net 2/2] Revert "net: txgbe: fix clk_name exceed MAX_DEV_ID limits" Duanqiang Wen
2024-04-22 23:22 ` Jacob Keller
2024-04-22 23:26 ` [PATCH net 1/2] Revert "net: txgbe: fix i2c dev name cannot match clkdev" Jacob Keller
2024-04-25 3:00 ` 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=171401402832.32160.14071159006302877526.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=duanqiangwen@net-swift.com \
--cc=edumazet@google.com \
--cc=jiawenwu@trustnetic.com \
--cc=kuba@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=mengyuanlou@net-swift.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).