linux-kernel - Re: [PATCH 2/5] phy: iproc-mdio: Initial iProc MDC/MDIO support

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 21 May 2015 09:41:34 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	Ray Jui <rjui@...adcom.com>
Cc:	Kishon Vijay Abraham I <kishon@...com>,
	linux-kernel@...r.kernel.org,
	"JD (Jiandong) Zheng" <jdzheng@...adcom.com>,
	Arun Parameswaran <arunp@...adcom.com>,
	bcm-kernel-feedback-list@...adcom.com
Subject: Re: [PATCH 2/5] phy: iproc-mdio: Initial iProc MDC/MDIO support

On Tue, 2015-05-19 at 18:23 -0700, Ray Jui wrote:
> --- a/drivers/phy/Kconfig
> +++ b/drivers/phy/Kconfig
>  
> +config PHY_IPROC_MDIO
> +	bool "Broadcom iProc MDC/MDIO driver"
> +	depends on ARCH_BCM_IPROC
> +	default ARCH_BCM_IPROC
> +	help
> +	  Enable this to support the iProc generic MDC/MDIO interface found
> +	  in various iProc based SoCs. The generic MDC/MDIO interface can be
> +	  used to communicate with various types of Serdes/PHYs including
> +	  Ethernet, PCIe, USB, and etc.
> +
> +	  If unsure, say N.

> --- a/drivers/phy/Makefile
> +++ b/drivers/phy/Makefile

> +obj-$(CONFIG_PHY_IPROC_MDIO)		+= phy-iproc-mdio.o

> --- /dev/null
> +++ b/drivers/phy/phy-iproc-mdio.c

> +#include <linux/module.h>

> +static int __init iproc_mdio_init(void)
> +{
> +	return platform_driver_register(&iproc_mdio_driver);
> +}
> +arch_initcall_sync(iproc_mdio_init);
> +
> +MODULE_AUTHOR("Ray Jui <rjui@...adcom.com>");
> +MODULE_DESCRIPTION("Broadcom iPROC MDC/MDIO driver");
> +MODULE_LICENSE("GPL v2");

I guess phy-iproc-mdio.o is intended to be built-in only. If that's
correct the above three MODULE_ macros (and, probably, the include of
linux/module.h) can safely be dropped.

Thanks,


Paul Bolle

--
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/