Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755802Ab2F1RF5 (ORCPT ); Thu, 28 Jun 2012 13:05:57 -0400 Received: from mail-pz0-f46.google.com ([209.85.210.46]:42391 "EHLO mail-pz0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754247Ab2F1RF4 (ORCPT ); Thu, 28 Jun 2012 13:05:56 -0400 Message-ID: <4FEC8EF0.6080408@gmail.com> Date: Thu, 28 Jun 2012 10:05:52 -0700 From: David Daney User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.15) Gecko/20101027 Fedora/3.0.10-1.fc12 Thunderbird/3.0.10 MIME-Version: 1.0 To: David Miller CC: grant.likely@secretlab.ca, rob.herring@calxeda.com, devicetree-discuss@lists.ozlabs.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mips@linux-mips.org, afleming@gmail.com, david.daney@cavium.com Subject: Re: [PATCH v2 0/4] netdev/phy: 10G PHY support. References: <1340818418-10382-1-git-send-email-ddaney.cavm@gmail.com> <20120627.212941.485325944406335522.davem@davemloft.net> In-Reply-To: <20120627.212941.485325944406335522.davem@davemloft.net> Content-Type: text/plain; charset=ISO-8859-7; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2107 Lines: 63 On 06/27/2012 09:29 PM, David Miller wrote: > From: David Daney > Date: Wed, 27 Jun 2012 10:33:34 -0700 > >> From: David Daney >> >> The only non-cosmetic change from v1 is to pass an additional argument >> to get_phy_device() that indicates that the PHY uses 802.3 clause 45 >> signaling, previously I had been using a high order bit of the addr >> parameter for this. >> >> There are also changes from v1 in the code and comment formatting. >> These should now be closer to what David Miller prefers. > > Applied, but I had to add the following warning fixup: Thank You. > > -------------------- > phy: Fix warning in get_phy_device(). > > drivers/net/phy/phy_device.c: In function ?get_phy_device?: > drivers/net/phy/phy_device.c:340:14: warning: ?phy_id? may be used uninitialized in this function [-Wmaybe-uninitialized] > > GCC can't see that when we return zero we always initialize > phy_id and that's the only path where we use it. > > Initialize phy_id to zero to shut it up. > FWIW: I was testing with GCC-4.6.3 and saw no such warnings. David Daney > Signed-off-by: David S. Miller > --- > drivers/net/phy/phy_device.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/net/phy/phy_device.c b/drivers/net/phy/phy_device.c > index ef4cdee..47e02e7 100644 > --- a/drivers/net/phy/phy_device.c > +++ b/drivers/net/phy/phy_device.c > @@ -327,9 +327,9 @@ static int get_phy_id(struct mii_bus *bus, int addr, u32 *phy_id, > */ > struct phy_device *get_phy_device(struct mii_bus *bus, int addr, bool is_c45) > { > - struct phy_device *dev = NULL; > - u32 phy_id; > struct phy_c45_device_ids c45_ids = {0}; > + struct phy_device *dev = NULL; > + u32 phy_id = 0; > int r; > > r = get_phy_id(bus, addr,&phy_id, is_c45,&c45_ids); -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/