linux-kernel - Re: [PATCH] phy: armada375-usb2: Set drvdata for phy and use it

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 25 Feb 2015 21:08:49 +0530
From:	Kishon Vijay Abraham I <kishon@...com>
To:	Axel Lin <axel.lin@...ics.com>
CC:	Gregory CLEMENT <gregory.clement@...e-electrons.com>,
	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] phy: armada375-usb2: Set drvdata for phy and use it



On Tuesday 24 February 2015 07:42 PM, Axel Lin wrote:
> Signed-off-by: Axel Lin <axel.lin@...ics.com>

need a commit msg pls.

-Kishon

> ---
>   drivers/phy/phy-armada375-usb2.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/phy/phy-armada375-usb2.c b/drivers/phy/phy-armada375-usb2.c
> index 7c99ca2..8ccc395 100644
> --- a/drivers/phy/phy-armada375-usb2.c
> +++ b/drivers/phy/phy-armada375-usb2.c
> @@ -37,7 +37,7 @@ static int armada375_usb_phy_init(struct phy *phy)
>   	struct armada375_cluster_phy *cluster_phy;
>   	u32 reg;
>
> -	cluster_phy = dev_get_drvdata(phy->dev.parent);
> +	cluster_phy = phy_get_drvdata(phy);
>   	if (!cluster_phy)
>   		return -ENODEV;
>
> @@ -131,6 +131,7 @@ static int armada375_usb_phy_probe(struct platform_device *pdev)
>   	cluster_phy->reg = usb_cluster_base;
>
>   	dev_set_drvdata(dev, cluster_phy);
> +	phy_set_drvdata(phy, cluster_phy);
>
>   	phy_provider = devm_of_phy_provider_register(&pdev->dev,
>   						     armada375_usb_phy_xlate);
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/