Received: by 10.223.164.202 with SMTP id h10csp352423wrb; Wed, 8 Nov 2017 18:05:35 -0800 (PST) X-Google-Smtp-Source: ABhQp+RjmlfNA8HoTpPvIvB5yB/L4RmHopxfgOoZDYEWFLOYYnGC4WAdZEuEIZC2hcXl7k4VgRft X-Received: by 10.84.238.136 with SMTP id v8mr2219414plk.37.1510193135125; Wed, 08 Nov 2017 18:05:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510193135; cv=none; d=google.com; s=arc-20160816; b=mGRf9z15pj1szkKMjBLXCfggvf3ojSnhkMqyFEfOpUo3OQzIRCXAdgaL1e9ksB62Rg dfxo1QbdDuLlvufMBKy/jnaI4WPReReCj+TPYupCQJhjsi3EDbNPX/Gl1bpUn2F+Cxfn 4uN3P8+O7ReIh4TCmvfICVkN/lEnyZrQBTonD0MSiOocvkwlYSNVJ275Yc655m1WJ65B maVPU9H23NbG1M8JNXwxtE69bruChLEkxQXqqHRXHKWsXVWiMrU4m6o0xxCZhxVzz5TR VkQAnC6if4QoLlUzC4IhebS5mlp1xycMuFMZ3LvUiotBRIzrRurBx+zVLuVbDEevj60Y VG0A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:cc:references:to :subject:arc-authentication-results; bh=FV905aJQvDfmLiL9x2tJGUtmyNOHqub01Lq1uRpReJo=; b=la+lGBamnNAhz9Pb0olZ0+hebs+K4XTsKcL8w8wWqGiwQjD8EjvdmQHsegLk3GeBwk 7dhuANhO46c4B8q4C+4HMBb4HKM1kWdyQQVEHtJoTg+IKIU4E6RBU5OiHiFnWEmZPt2+ t/fdUeBcHdz71WCIg6n1sQ87bV2e+w29iiv7Budm2c/cdCxBUJeUx0FWAq19k9ryTcCk PTbwh42SkZua+dEQDkMZop7E0Co6uCx/V5TCWRTc5ehpdqKeUujGZqBWUTK4+CnC/wgF 1TD4xpumfJpUfOYKNSWl8+euCMVrjuncu74yQO6r2EJhPsrl1oGDVPeyukErEDB/tM0v /deQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h86si5524183pfj.24.2017.11.08.18.05.23; Wed, 08 Nov 2017 18:05:35 -0800 (PST) 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; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752503AbdKICDT (ORCPT + 82 others); Wed, 8 Nov 2017 21:03:19 -0500 Received: from szxga06-in.huawei.com ([45.249.212.32]:45310 "EHLO huawei.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1752328AbdKICDR (ORCPT ); Wed, 8 Nov 2017 21:03:17 -0500 Received: from DGGEMS409-HUB.china.huawei.com (unknown [172.30.72.58]) by Forcepoint Email with ESMTP id 906B4C2225BF9; Thu, 9 Nov 2017 10:03:03 +0800 (CST) Received: from [127.0.0.1] (10.63.173.108) by DGGEMS409-HUB.china.huawei.com (10.3.19.209) with Microsoft SMTP Server id 14.3.361.1; Thu, 9 Nov 2017 10:02:38 +0800 Subject: Re: [PATCH net-next 1/2] net: hns3: fix a bug when getting phy address from NCL_config file To: Andrew Lunn References: <1510127543-34158-1-git-send-email-lipeng321@huawei.com> <1510127543-34158-2-git-send-email-lipeng321@huawei.com> <20171108143052.GH21784@lunn.ch> CC: , , , , , From: "lipeng (Y)" Message-ID: Date: Thu, 9 Nov 2017 10:02:37 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20171108143052.GH21784@lunn.ch> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.63.173.108] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2017/11/8 22:30, Andrew Lunn wrote: > On Wed, Nov 08, 2017 at 03:52:22PM +0800, Lipeng wrote: >> From: Fuyun Liang >> >> 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? The PHY address is still 5 bits, but do you need to > get the device type from your configuration file? > > Andrew Hi Andrew C45 support is in Plan, now only support C22. This bugfix patch is valid for C22 and C45. As plan , will get the device type(NULL, C22, C45) from configuration file after support C45. Do you think we must do it now? or can add it along with C45 support? Lipeng > . > From 1583509249569054846@xxx Wed Nov 08 14:41:41 +0000 2017 X-GM-THRID: 1583483607446527794 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread