Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp3223993imm; Sun, 29 Jul 2018 13:17:39 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcdICYC8FzOXixkrVEdGApy4WXk9NvbTfw0wGUh0PqohxiwQR5G0VSfTTZwc09HSwrG+k7Z X-Received: by 2002:a63:2a0b:: with SMTP id q11-v6mr13729210pgq.36.1532895459230; Sun, 29 Jul 2018 13:17:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532895459; cv=none; d=google.com; s=arc-20160816; b=WIz6QwzRnPW7y2nXuF9c36xOcT2wqgXjrtfe90RvH1DptkE7dT5sMVw94hJUUW7lck VFCZ6FW6q6V2euTRrgxbEg+qWNzwJsZS39rqSNGs6rwQLhbi1T64dttfegeyzXzcNWsu tvc/WRAoCHnKt6a3S7jFMaNT/p7AbnNvsFDEnvLY7ufInYH2uVdAxt8H0I2UFmopVJ9e OZRAIbOXpztPGalYGSMsqtDKEhtwpqx5bpV8FN2c6H8pSQXvXZRGF0wzKtQSz9ulkhSu 5xD7v4D6VP5X9AGEnwcv2ojOBtvzsxvYqZv1Z3DfF3xjd/z31+B0kiWHW0HGhpKWQBsv b+dw== 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:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date :arc-authentication-results; bh=b7qx+GYa81EQfEO0z9P/jNZHfE+vLLKuGOMAnz0B9o0=; b=LykUZAarf25GUbtCOVxqJagh3u98QoSPehbH2qR2CjMAD64UwHzZjCklJToWBhXEQS D4iTQtbI5vINQf8Iid9pcWAdAN6ucbcAHN5kFs+/aYHgRiXIHpYZ8N5iB3zygEF2gECJ 6AyrbWemsZgwdEckc3Z489l+pMISe7rsksVhx0sVxw5WV2Cc56/wC36Xs/KzQUAZEhVK zbChovixYqcXBoRbWlS9vLI9vHeS74vYrA9zCOHBGSOpcKpHEJns7LUZAVBLv9LtMXKJ FCPpnwMIsY1cdKGrnNX4CEycafEdrTtSHHuSPzt7I37p+XzXwxPeU1dfhE0R2MxNQD39 SnSg== 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 l6-v6si9080620pgl.567.2018.07.29.13.17.25; Sun, 29 Jul 2018 13:17:39 -0700 (PDT) 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 S1729378AbeG2VsC (ORCPT + 99 others); Sun, 29 Jul 2018 17:48:02 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:44464 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726813AbeG2VsC (ORCPT ); Sun, 29 Jul 2018 17:48:02 -0400 Received: from localhost (c-73-37-107-99.hsd1.or.comcast.net [73.37.107.99]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id 9233113E47D63; Sun, 29 Jul 2018 13:16:21 -0700 (PDT) Date: Sun, 29 Jul 2018 13:16:21 -0700 (PDT) Message-Id: <20180729.131621.773833672945325604.davem@davemloft.net> To: sean.wang@mediatek.com Cc: john@phrozen.org, nbd@openwrt.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org Subject: Re: [PATCH net-next 2/2] net-next: mediatek: cleanup unnecessary get chip id and its user From: David Miller In-Reply-To: References: <658dfd485c035cdae5452bc5d572125076b47a48.1532755541.git.sean.wang@mediatek.com> X-Mailer: Mew version 6.7 on Emacs 26 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Sun, 29 Jul 2018 13:16:21 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Date: Sat, 28 Jul 2018 13:35:56 +0800 > From: Sean Wang > > Since driver is devicetree-based, all device type and charateristic can be > determined by the compatible string and its data. It's unnecessary to > create another dependent function to check chip ID and then decide whether > the specific funciton is being supported on a certain device. It can be > totally replaced by the existing flag, so a cleanup is made by removing > the function and the only user, HWLRO. > > MT2701 also have a missing HWLRO support in old code, so add it the same > patch. > > Signed-off-by: Sean Wang Applied.