Received: by 2002:a25:b794:0:0:0:0:0 with SMTP id n20csp7310951ybh; Thu, 8 Aug 2019 13:34:09 -0700 (PDT) X-Google-Smtp-Source: APXvYqz2qvxQCRxE3a36e5zbExJbV5FRjEHSzxygg2jCaQuJln39M9D9SyRElVC7tu3bJBNZ/Cd+ X-Received: by 2002:a63:125c:: with SMTP id 28mr14346680pgs.255.1565296449469; Thu, 08 Aug 2019 13:34:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565296449; cv=none; d=google.com; s=arc-20160816; b=xUAHPjCDEct2bfuqaXCfgugymgL0UkkuNWntoRe5UByPoHqEfphzh8hDiTCggN+oPJ KKiMsq72b/L+JEO/tNMS3RNp/rUkGf0zQSv0CGj/bRVAdS5eh4pmG5cjY6ONshCzFXBr DGD329JvKYj3esCCkyAsF2IR9hgMGmJKIk/+7+RLlpM+98lMNKa6cGAUJObtmx2QYp1C dBCZBSkEZhC1C00jkzika/GDy4/MUSxV5eJh5W+t95C2mnIfOyHMILOySYicw9ZD1JeU BTF/RsceDof6krOB08BfoPNZDM2Ec+TzjW9rsM7d6BTxeuE+eZitZ2feSMqt0sU/PjKW 7l1g== 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; bh=JwMaRrX3w4D/Ph71EqE4NY1LxDayMCurd9Tda0Boe+A=; b=ULBlF8+748KjSrefX4scUQ/k/3RiHHj6nMy8glwfpEa23MkOOEEP50XDWvj/v3FNRr qQ2d+UYu3Ji1rwAiXMyRpWjqI/T+I/os3jmKpBvuUax9TTxmhKle73El60keYjNMdnjG MZWA4GeeG67zOsSX7GZF7QUHpC+aWbIL8/jYnt1dha4x+fjEPeWZU8PNrBq3oSQk8rG8 7gdmhjxZKKjMaG60Xo4pd2EzZHyQ1QmGSfZgDPNRtHWKngf8f+WWHc6J8oCxsZgLY65a bRD24IRz+Qwj3qpQSVkD1NWdkQP48J6XIgV7ZjYVywVmbQJ9XgSSyMLyKjjn+drctO4s CSUA== 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 r23si5883616pgv.451.2019.08.08.13.33.52; Thu, 08 Aug 2019 13:34:09 -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 S2389823AbfHHSiO (ORCPT + 99 others); Thu, 8 Aug 2019 14:38:14 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:49586 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725535AbfHHSiO (ORCPT ); Thu, 8 Aug 2019 14:38:14 -0400 Received: from localhost (unknown [IPv6:2601:601:9f80:35cd::d71]) (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 8F1AE154FA021; Thu, 8 Aug 2019 11:38:13 -0700 (PDT) Date: Thu, 08 Aug 2019 11:38:13 -0700 (PDT) Message-Id: <20190808.113813.478689798535715440.davem@davemloft.net> To: yuehaibing@huawei.com Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us, vinicius.gomes@intel.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org Subject: Re: [PATCH net-next] taprio: remove unused variable 'entry_list_policy' From: David Miller In-Reply-To: <20190808142623.69188-1-yuehaibing@huawei.com> References: <20190808142623.69188-1-yuehaibing@huawei.com> X-Mailer: Mew version 6.8 on Emacs 26.1 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]); Thu, 08 Aug 2019 11:38:13 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: YueHaibing Date: Thu, 8 Aug 2019 22:26:23 +0800 > net/sched/sch_taprio.c:680:32: warning: > entry_list_policy defined but not used [-Wunused-const-variable=] > > It is not used since commit a3d43c0d56f1 ("taprio: Add > support adding an admin schedule") > > Reported-by: Hulk Robot > Signed-off-by: YueHaibing This is probably unintentional and a bug, we should be using that policy value to validate that the sched list is indeed a nested attribute. I'm not applying this without at least a better and clear commit message explaining why we shouldn't be using this policy any more.