From: patchwork-bot+netdevbpf@kernel.org
To: Michael Sit Wei Hong <michael.wei.hong.sit@intel.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, tee.min.tan@intel.com,
kuan.loon.lay@intel.com, boon.leong.ong@intel.com,
hong.aun.looi@intel.com, weifeng.voon@intel.com,
muhammad.husaini.zulkifli@intel.com, yi.fang.gan@intel.com
Subject: Re: [PATCH net v2 RESEND 1/1] net: phy: dp83867: Fix SGMII FIFO depth for non OF devices
Date: Sat, 12 Nov 2022 05:10:17 +0000 [thread overview]
Message-ID: <166822981737.20406.12251689549170298755.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221110054938.925347-1-michael.wei.hong.sit@intel.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 10 Nov 2022 13:49:38 +0800 you wrote:
> Current driver code will read device tree node information,
> and set default values if there is no info provided.
>
> This is not done in non-OF devices leading to SGMII fifo depths being
> set to the smallest size.
>
> This patch sets the value to the default value of the PHY as stated in the
> PHY datasheet.
>
> [...]
Here is the summary with links:
- [net,v2,RESEND,1/1] net: phy: dp83867: Fix SGMII FIFO depth for non OF devices
https://git.kernel.org/netdev/net/c/e2a54350dc96
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-12 5:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 5:49 [PATCH net v2 RESEND 1/1] net: phy: dp83867: Fix SGMII FIFO depth for non OF devices Michael Sit Wei Hong
2022-11-10 13:09 ` Andrew Lunn
2022-11-12 5: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=166822981737.20406.12251689549170298755.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=boon.leong.ong@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=hong.aun.looi@intel.com \
--cc=kuan.loon.lay@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael.wei.hong.sit@intel.com \
--cc=muhammad.husaini.zulkifli@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tee.min.tan@intel.com \
--cc=weifeng.voon@intel.com \
--cc=yi.fang.gan@intel.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