netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	andersson@kernel.org, konrad.dybcio@linaro.org, andrew@lunn.ch,
	hkallweit1@gmail.com, linux@armlinux.org.uk,
	florian.fainelli@broadcom.com,
	bcm-kernel-feedback-list@broadcom.com, robert.marko@sartura.hr,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [net-next PATCH v7 00/10] net: phy: Introduce PHY Package concept
Date: Sat, 10 Feb 2024 15:40:31 +0000	[thread overview]
Message-ID: <170757963125.14284.2496460448206023966.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240206173115.7654-1-ansuelsmth@gmail.com>

Hello:

This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:

On Tue,  6 Feb 2024 18:31:03 +0100 you wrote:
> Idea of this big series is to introduce the concept of PHY package in DT
> and give PHY drivers a way to derive the base address from DT.
> 
> The concept of PHY package is nothing new and is already a thing in the
> kernel with the API phy_package_join/leave/read/write.
> 
> What is currently lacking is describing this in DT and better reference
> a base address to calculate offset from.
> 
> [...]

Here is the summary with links:
  - [net-next,v7,01/10] dt-bindings: net: document ethernet PHY package nodes
    https://git.kernel.org/netdev/net-next/c/8453c88c7a15
  - [net-next,v7,02/10] net: phy: add support for scanning PHY in PHY packages nodes
    https://git.kernel.org/netdev/net-next/c/385ef48f4686
  - [net-next,v7,03/10] net: phy: add devm/of_phy_package_join helper
    https://git.kernel.org/netdev/net-next/c/471e8fd3afce
  - [net-next,v7,04/10] net: phy: qcom: move more function to shared library
    https://git.kernel.org/netdev/net-next/c/737eb75a815f
  - [net-next,v7,05/10] dt-bindings: net: Document Qcom QCA807x PHY package
    https://git.kernel.org/netdev/net-next/c/dd87eaa13787
  - [net-next,v7,06/10] net: phy: provide whether link has changed in c37_read_status
    https://git.kernel.org/netdev/net-next/c/9b1d5e055508
  - [net-next,v7,07/10] net: phy: qcom: add support for QCA807x PHY Family
    https://git.kernel.org/netdev/net-next/c/d1cb613efbd3
  - [net-next,v7,08/10] net: phy: qcom: move common qca808x LED define to shared header
    https://git.kernel.org/netdev/net-next/c/ee9d9807bee0
  - [net-next,v7,09/10] net: phy: qcom: generalize some qca808x LED functions
    https://git.kernel.org/netdev/net-next/c/47b930d0dd43
  - [net-next,v7,10/10] net: phy: qca807x: add support for configurable LED
    https://git.kernel.org/netdev/net-next/c/f508a226b517

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-02-10 15:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06 17:31 [net-next PATCH v7 00/10] net: phy: Introduce PHY Package concept Christian Marangi
2024-02-06 17:31 ` [net-next PATCH v7 01/10] dt-bindings: net: document ethernet PHY package nodes Christian Marangi
2024-02-06 17:31 ` [net-next PATCH v7 02/10] net: phy: add support for scanning PHY in PHY packages nodes Christian Marangi
2024-02-10  1:17   ` Andrew Lunn
2024-02-06 17:31 ` [net-next PATCH v7 03/10] net: phy: add devm/of_phy_package_join helper Christian Marangi
2024-02-10  1:20   ` Andrew Lunn
2024-02-06 17:31 ` [net-next PATCH v7 04/10] net: phy: qcom: move more function to shared library Christian Marangi
2024-02-10  1:21   ` Andrew Lunn
2024-02-06 17:31 ` [net-next PATCH v7 05/10] dt-bindings: net: Document Qcom QCA807x PHY package Christian Marangi
2024-02-10  1:23   ` Andrew Lunn
2024-02-06 17:31 ` [net-next PATCH v7 06/10] net: phy: provide whether link has changed in c37_read_status Christian Marangi
2024-02-10  1:29   ` Andrew Lunn
2024-02-06 17:31 ` [net-next PATCH v7 07/10] net: phy: qcom: add support for QCA807x PHY Family Christian Marangi
2024-02-10  1:40   ` Andrew Lunn
2024-02-06 17:31 ` [net-next PATCH v7 08/10] net: phy: qcom: move common qca808x LED define to shared header Christian Marangi
2024-02-10  1:41   ` Andrew Lunn
2024-02-06 17:31 ` [net-next PATCH v7 09/10] net: phy: qcom: generalize some qca808x LED functions Christian Marangi
2024-02-06 17:31 ` [net-next PATCH v7 10/10] net: phy: qca807x: add support for configurable LED Christian Marangi
2024-02-10 15: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=170757963125.14284.2496460448206023966.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andersson@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=ansuelsmth@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=hkallweit1@gmail.com \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robert.marko@sartura.hr \
    --cc=robh+dt@kernel.org \
    /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).