Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Salil Mehta <salil.mehta@huawei.com>
To:     Andrew Lunn <andrew@lunn.ch>, "lipeng (Y)" <lipeng321@huawei.com>
CC:     "davem@davemloft.net" <davem@davemloft.net>,
        "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Linuxarm <linuxarm@huawei.com>,
        "Zhuangyuzeng (Yisen)" <yisen.zhuang@huawei.com>
Subject: RE: [PATCH net-next 1/2] net: hns3: fix a bug when getting phy
 address from NCL_config file
Thread-Topic: [PATCH net-next 1/2] net: hns3: fix a bug when getting phy
 address from NCL_config file
Thread-Index: AQHTWGJvrPGDinnzqkGNTGa0Li6LLqMKetMAgAASM1A=
Date:   Wed, 8 Nov 2017 14:40:30 +0000
Message-ID: <F4CC6FACFEB3C54C9141D49AD221F7F93B9684BF@FRAEML521-MBX.china.huawei.com>
References: <1510127543-34158-1-git-send-email-lipeng321@huawei.com>
 <1510127543-34158-2-git-send-email-lipeng321@huawei.com>
 <20171108143052.GH21784@lunn.ch>
In-Reply-To: <20171108143052.GH21784@lunn.ch>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8BIT
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi Andrew,

> -----Original Message-----
> From: Andrew Lunn [mailto:andrew@lunn.ch]
> Sent: Wednesday, November 08, 2017 2:31 PM
> To: lipeng (Y)
> Cc: davem@davemloft.net; netdev@vger.kernel.org; linux-
> kernel@vger.kernel.org; Linuxarm; Zhuangyuzeng (Yisen); Salil Mehta
> Subject: Re: [PATCH net-next 1/2] net: hns3: fix a bug when getting phy
> address from NCL_config file
> 
> On Wed, Nov 08, 2017 at 03:52:22PM +0800, Lipeng wrote:
> > From: Fuyun Liang <liangfuyun1@huawei.com>
> >
> > Driver gets phy address from NCL_config file and uses the phy address
> > to initialize phydev. There are 5 bits for phy address. And C22 phy
> > address has 5 bits. So 0-31 are all valid address for phy. If there
> > is no phy, it will crash. Because driver always get a valid phy
> address.
> 
> Hi Lipeng
> 
> Any plans for C45? 
Still remember the kernel change required to support C45 discussed with
you some time back :). Will try to push that change as soon as possible.
And yes, we would be pushing the support of the C45 for HNS3 driver as
well after that.

Thanks
Salil

From 1583508678802976816@xxx Wed Nov 08 14:32:36 +0000 2017
X-GM-THRID: 1583483607446527794
X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread