Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751598AbdL0BPK (ORCPT ); Tue, 26 Dec 2017 20:15:10 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:56542 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751211AbdL0BPJ (ORCPT ); Tue, 26 Dec 2017 20:15:09 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 8BBA260B1B Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=sboyd@codeaurora.org Date: Tue, 26 Dec 2017 17:15:07 -0800 From: Stephen Boyd To: sean.wang@mediatek.com Cc: mturquette@baylibre.com, matthias.bgg@gmail.com, jdelvare@suse.de, jamesjj.liao@mediatek.com, weiyi.lu@mediatek.com, kevin-cw.chen@mediatek.com, shunli.wang@mediatek.com, chen.zhong@mediatek.com, arnd@arndb.de, linux-mediatek@lists.infradead.org, linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] clk: mediatek: remove superfluous line including linux/clk-provider.h Message-ID: <20171227011507.GR7997@codeaurora.org> References: <96d2fcd536d75dbbfde0aa0ad0797e80da89117b.1514191770.git.sean.wang@mediatek.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <96d2fcd536d75dbbfde0aa0ad0797e80da89117b.1514191770.git.sean.wang@mediatek.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 918 Lines: 23 On 12/25, sean.wang@mediatek.com wrote: > From: Sean Wang > > clk-mtk.h has already included linux/clk-provider.h inside, so remove > the superfluous line including linux/clk-provider.h from these files which > also included clk-mtk.h. > > Signed-off-by: Sean Wang > Cc: Jean Delvare > --- Please don't do this. If anything, I would remove as many includes from clk-mtk.h as possible and forward declare the structures used in there so there isn't any header dependency. Then it becomes clear which C files are clk-provider drivers almost immediately because we have the include in the driver, and we also avoid any header dependency chains where we must include some header file if we want to get another header file's definitions. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project