netdev - Re: [PATCH net-next 1/1] amd-xgbe: fix unused variable compilation warning in phylib driver

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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 9 Jun 2014 14:07:28 -0500
From:	Tom Lendacky <thomas.lendacky@....com>
To:	Francois Romieu <romieu@...zoreil.com>, <netdev@...r.kernel.org>
CC:	David Miller <davem@...emloft.net>
Subject: Re: [PATCH net-next 1/1] amd-xgbe: fix unused variable compilation
 warning in phylib driver

On 06/07/2014 04:07 AM, Francois Romieu wrote:
> Fix following compilation warning:
> [...]
>    CC      drivers/net/phy/amd-xgbe-phy.o
> drivers/net/phy/amd-xgbe-phy.c:1353:30: warning:
> ‘amd_xgbe_phy_ids’ defined but not used [-Wunused-variable]
>   static struct mdio_device_id amd_xgbe_phy_ids[] = {
>                                ^
> Signed-off-by: Francois Romieu <romieu@...zoreil.com>

Acked-by: Tom Lendacky <thomas.lendacky@....com>

> ---
>   drivers/net/phy/amd-xgbe-phy.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/phy/amd-xgbe-phy.c b/drivers/net/phy/amd-xgbe-phy.c
> index d4b1c81..b57c224 100644
> --- a/drivers/net/phy/amd-xgbe-phy.c
> +++ b/drivers/net/phy/amd-xgbe-phy.c
> @@ -1350,7 +1350,7 @@ static void __exit amd_xgbe_phy_exit(void)
>   module_init(amd_xgbe_phy_init);
>   module_exit(amd_xgbe_phy_exit);
>
> -static struct mdio_device_id amd_xgbe_phy_ids[] = {
> +static struct mdio_device_id __maybe_unused amd_xgbe_phy_ids[] = {
>   	{ XGBE_PHY_ID, XGBE_PHY_MASK },
>   	{ }
>   };
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html