All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: vladimir.oltean@nxp.com
Cc: linux-phy@lists.infradead.org, Vinod Koul <vkoul@kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org,
	linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, linux-can@vger.kernel.org,
	linux-gpio@vger.kernel.org, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	linux-pci@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-riscv@lists.infradead.org,
	linux-rockchip@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-sunxi@lists.linux.dev,
	linux-tegra@vger.kernel.org, linux-usb@vger.kernel.org,
	netdev@vger.kernel.org, spacemit@lists.linux.dev,
	UNGLinuxDriver@microchip.com,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Shawn Lin <shawn.lin@rock-chips.com>
Subject: Re: [PATCH v2 phy-next 22/24] phy: include PHY provider header (2/2)
Date: Sun, 8 Mar 2026 12:01:36 +0000	[thread overview]
Message-ID: <aa1lIBO3j_apIPjb@shell.armlinux.org.uk> (raw)
In-Reply-To: <20260308114009.2546587-23-vladimir.oltean@nxp.com>

On Sun, Mar 08, 2026 at 01:40:07PM +0200, vladimir.oltean@nxp.com wrote:
> diff --git a/drivers/phy/qualcomm/phy-qcom-sgmii-eth.c b/drivers/phy/qualcomm/phy-qcom-sgmii-eth.c
> index 5b1c82459c12..4f8ffc6524ab 100644
> --- a/drivers/phy/qualcomm/phy-qcom-sgmii-eth.c
> +++ b/drivers/phy/qualcomm/phy-qcom-sgmii-eth.c
> @@ -7,10 +7,11 @@
>  #include <linux/ethtool.h>
>  #include <linux/module.h>
>  #include <linux/of.h>
> -#include <linux/phy/phy.h>
>  #include <linux/platform_device.h>
>  #include <linux/regmap.h>
>  
> +#include "../phy-provider.h"
> +

As we know, this will conflict with my patch in net-next. I guess Vinod
hasn't (yet?) merged the commit that Jakub provided.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!


WARNING: multiple messages have this Message-ID (diff)
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: vladimir.oltean@nxp.com
Cc: linux-phy@lists.infradead.org, Vinod Koul <vkoul@kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org,
	linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, linux-can@vger.kernel.org,
	linux-gpio@vger.kernel.org, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	linux-pci@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-riscv@lists.infradead.org,
	linux-rockchip@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-sunxi@lists.linux.dev,
	linux-tegra@vger.kernel.org, linux-usb@vger.kernel.org,
	netdev@vger.kernel.org, spacemit@lists.linux.dev,
	UNGLinuxDriver@microchip.com,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Shawn Lin <shawn.lin@rock-chips.com>
Subject: Re: [PATCH v2 phy-next 22/24] phy: include PHY provider header (2/2)
Date: Sun, 8 Mar 2026 12:01:36 +0000	[thread overview]
Message-ID: <aa1lIBO3j_apIPjb@shell.armlinux.org.uk> (raw)
In-Reply-To: <20260308114009.2546587-23-vladimir.oltean@nxp.com>

On Sun, Mar 08, 2026 at 01:40:07PM +0200, vladimir.oltean@nxp.com wrote:
> diff --git a/drivers/phy/qualcomm/phy-qcom-sgmii-eth.c b/drivers/phy/qualcomm/phy-qcom-sgmii-eth.c
> index 5b1c82459c12..4f8ffc6524ab 100644
> --- a/drivers/phy/qualcomm/phy-qcom-sgmii-eth.c
> +++ b/drivers/phy/qualcomm/phy-qcom-sgmii-eth.c
> @@ -7,10 +7,11 @@
>  #include <linux/ethtool.h>
>  #include <linux/module.h>
>  #include <linux/of.h>
> -#include <linux/phy/phy.h>
>  #include <linux/platform_device.h>
>  #include <linux/regmap.h>
>  
> +#include "../phy-provider.h"
> +

As we know, this will conflict with my patch in net-next. I guess Vinod
hasn't (yet?) merged the commit that Jakub provided.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

WARNING: multiple messages have this Message-ID (diff)
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: vladimir.oltean@nxp.com
Cc: linux-phy@lists.infradead.org, Vinod Koul <vkoul@kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org,
	linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, linux-can@vger.kernel.org,
	linux-gpio@vger.kernel.org, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	linux-pci@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-riscv@lists.infradead.org,
	linux-rockchip@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-sunxi@lists.linux.dev,
	linux-tegra@vger.kernel.org, linux-usb@vger.kernel.org,
	netdev@vger.kernel.org, spacemit@lists.linux.dev,
	UNGLinuxDriver@microchip.com,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Shawn Lin <shawn.lin@rock-chips.com>
Subject: Re: [PATCH v2 phy-next 22/24] phy: include PHY provider header (2/2)
Date: Sun, 8 Mar 2026 12:01:36 +0000	[thread overview]
Message-ID: <aa1lIBO3j_apIPjb@shell.armlinux.org.uk> (raw)
In-Reply-To: <20260308114009.2546587-23-vladimir.oltean@nxp.com>

On Sun, Mar 08, 2026 at 01:40:07PM +0200, vladimir.oltean@nxp.com wrote:
> diff --git a/drivers/phy/qualcomm/phy-qcom-sgmii-eth.c b/drivers/phy/qualcomm/phy-qcom-sgmii-eth.c
> index 5b1c82459c12..4f8ffc6524ab 100644
> --- a/drivers/phy/qualcomm/phy-qcom-sgmii-eth.c
> +++ b/drivers/phy/qualcomm/phy-qcom-sgmii-eth.c
> @@ -7,10 +7,11 @@
>  #include <linux/ethtool.h>
>  #include <linux/module.h>
>  #include <linux/of.h>
> -#include <linux/phy/phy.h>
>  #include <linux/platform_device.h>
>  #include <linux/regmap.h>
>  
> +#include "../phy-provider.h"
> +

As we know, this will conflict with my patch in net-next. I guess Vinod
hasn't (yet?) merged the commit that Jakub provided.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

WARNING: multiple messages have this Message-ID (diff)
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: vladimir.oltean@nxp.com
Cc: linux-phy@lists.infradead.org, Vinod Koul <vkoul@kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org,
	linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, linux-can@vger.kernel.org,
	linux-gpio@vger.kernel.org, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	linux-pci@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-riscv@lists.infradead.org,
	linux-rockchip@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-sunxi@lists.linux.dev,
	linux-tegra@vger.kernel.org, linux-usb@vger.kernel.org,
	netdev@vger.kernel.org, spacemit@lists.linux.dev,
	UNGLinuxDriver@microchip.com,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Shawn Lin <shawn.lin@rock-chips.com>
Subject: Re: [PATCH v2 phy-next 22/24] phy: include PHY provider header (2/2)
Date: Sun, 8 Mar 2026 12:01:36 +0000	[thread overview]
Message-ID: <aa1lIBO3j_apIPjb@shell.armlinux.org.uk> (raw)
In-Reply-To: <20260308114009.2546587-23-vladimir.oltean@nxp.com>

On Sun, Mar 08, 2026 at 01:40:07PM +0200, vladimir.oltean@nxp.com wrote:
> diff --git a/drivers/phy/qualcomm/phy-qcom-sgmii-eth.c b/drivers/phy/qualcomm/phy-qcom-sgmii-eth.c
> index 5b1c82459c12..4f8ffc6524ab 100644
> --- a/drivers/phy/qualcomm/phy-qcom-sgmii-eth.c
> +++ b/drivers/phy/qualcomm/phy-qcom-sgmii-eth.c
> @@ -7,10 +7,11 @@
>  #include <linux/ethtool.h>
>  #include <linux/module.h>
>  #include <linux/of.h>
> -#include <linux/phy/phy.h>
>  #include <linux/platform_device.h>
>  #include <linux/regmap.h>
>  
> +#include "../phy-provider.h"
> +

As we know, this will conflict with my patch in net-next. I guess Vinod
hasn't (yet?) merged the commit that Jakub provided.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2026-03-08 12:02 UTC|newest]

Thread overview: 131+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-08 11:39 [PATCH v2 phy-next 00/24] Split Generic PHY consumer and provider API vladimir.oltean
2026-03-08 11:39 ` vladimir.oltean
2026-03-08 11:39 ` vladimir.oltean
2026-03-08 11:39 ` [PATCH v2 phy-next 01/24] ata: add <linux/pm_runtime.h> where missing vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39 ` [PATCH v2 phy-next 02/24] PCI: Add missing headers transitively included by <linux/phy/phy.h> vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39 ` [PATCH v2 phy-next 03/24] usb: add " vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39 ` [PATCH v2 phy-next 04/24] drm: add <linux/pm_runtime.h> where missing vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39 ` [PATCH v2 phy-next 05/24] phy: " vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39 ` [PATCH v2 phy-next 06/24] phy: spacemit: include missing <linux/phy/phy.h> vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39 ` [PATCH v2 phy-next 07/24] net: lan969x: include missing <linux/of.h> vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39 ` [PATCH v2 phy-next 08/24] PCI: Remove device links to PHY vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39 ` [PATCH v2 phy-next 09/24] ufs: exynos: stop poking into struct phy guts vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39 ` [PATCH v2 phy-next 10/24] drm/rockchip: dw_hdmi: avoid direct dereference of phy->dev.of_node vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39 ` [PATCH v2 phy-next 11/24] drm/msm/dp: remove debugging prints with internal struct phy state vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39 ` [PATCH v2 phy-next 12/24] phy: move provider API out of public <linux/phy/phy.h> vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39 ` [PATCH v2 phy-next 13/24] phy: make phy_get_mode(), phy_(get|set)_bus_width() NULL tolerant vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39 ` [PATCH v2 phy-next 14/24] phy: introduce phy_get_max_link_rate() helper for consumers vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-08 11:39   ` vladimir.oltean
2026-03-09  9:18   ` Markus Schneider-Pargmann
2026-03-09  9:18     ` Markus Schneider-Pargmann
2026-03-09  9:18     ` Markus Schneider-Pargmann
2026-03-09  9:18     ` Markus Schneider-Pargmann
2026-03-08 11:40 ` [PATCH v2 phy-next 15/24] drm/rockchip: dsi: include PHY provider header vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40 ` [PATCH v2 phy-next 16/24] drm: bridge: cdns-mhdp8546: use consumer API for getting PHY bus width vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40 ` [PATCH v2 phy-next 17/24] media: sunxi: a83-mips-csi2: include PHY provider header vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40 ` [PATCH v2 phy-next 18/24] net: renesas: rswitch: " vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40 ` [PATCH v2 phy-next 19/24] pinctrl: tegra-xusb: " vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40 ` [PATCH v2 phy-next 20/24] power: supply: cpcap-charger: include missing <linux/property.h> vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40 ` [PATCH v2 phy-next 21/24] phy: include PHY provider header (1/2) vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40 ` [PATCH v2 phy-next 22/24] phy: include PHY provider header (2/2) vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 12:01   ` Russell King (Oracle) [this message]
2026-03-08 12:01     ` Russell King (Oracle)
2026-03-08 12:01     ` Russell King (Oracle)
2026-03-08 12:01     ` Russell King (Oracle)
2026-03-08 12:37     ` Vladimir Oltean
2026-03-08 12:37       ` Vladimir Oltean
2026-03-08 12:37       ` Vladimir Oltean
2026-03-08 12:37       ` Vladimir Oltean
2026-03-08 11:40 ` [PATCH v2 phy-next 23/24] phy: remove temporary provider compatibility from consumer header vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40 ` [PATCH v2 phy-next 24/24] MAINTAINERS: add regexes for linux-phy vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 11:40   ` vladimir.oltean
2026-03-08 18:40   ` Joe Perches
2026-03-08 18:40     ` Joe Perches
2026-03-08 18:40     ` Joe Perches
2026-03-08 18:40     ` Joe Perches
2026-03-08 19:10     ` Vladimir Oltean
2026-03-08 19:10       ` Vladimir Oltean
2026-03-08 19:10       ` Vladimir Oltean
2026-03-08 19:10       ` Vladimir Oltean
2026-03-08 19:25       ` Joe Perches
2026-03-08 19:25         ` Joe Perches
2026-03-08 19:25         ` Joe Perches
2026-03-08 19:25         ` Joe Perches
2026-03-08 20:56         ` Vladimir Oltean
2026-03-08 20:56           ` Vladimir Oltean
2026-03-08 20:56           ` Vladimir Oltean
2026-03-08 20:56           ` Vladimir Oltean
2026-03-08 22:22           ` Joe Perches
2026-03-08 22:22             ` Joe Perches
2026-03-08 22:22             ` Joe Perches
2026-03-08 22:22             ` Joe Perches

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=aa1lIBO3j_apIPjb@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=netdev@vger.kernel.org \
    --cc=shawn.lin@rock-chips.com \
    --cc=spacemit@lists.linux.dev \
    --cc=vkoul@kernel.org \
    --cc=vladimir.oltean@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.