From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754689AbcGENc2 (ORCPT ); Tue, 5 Jul 2016 09:32:28 -0400 Received: from mail5.windriver.com ([192.103.53.11]:57079 "EHLO mail5.wrs.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751427AbcGENcZ (ORCPT ); Tue, 5 Jul 2016 09:32:25 -0400 Date: Tue, 5 Jul 2016 09:32:16 -0400 From: Paul Gortmaker To: Krzysztof Kozlowski CC: , Sylwester Nawrocki , Tomasz Figa , Michael Turquette , Stephen Boyd , Kukjin Kim , , Subject: Re: [PATCH 06/10] clk: samsung make clk-exynos-audss explicitly non-modular Message-ID: <20160705133216.GC26134@windriver.com> References: <20160704211220.5685-1-paul.gortmaker@windriver.com> <20160704211220.5685-7-paul.gortmaker@windriver.com> <577B782E.9090203@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <577B782E.9090203@samsung.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [Re: [PATCH 06/10] clk: samsung make clk-exynos-audss explicitly non-modular] On 05/07/2016 (Tue 11:04) Krzysztof Kozlowski wrote: > On 07/04/2016 11:12 PM, Paul Gortmaker wrote: > > The Kconfig currently controlling compilation of this code is: > > > > arch/arm/mach-exynos/Kconfig:menuconfig ARCH_EXYNOS > > arch/arm/mach-exynos/Kconfig: bool "Samsung EXYNOS" if ARCH_MULTI_V7 > > > > ...meaning that it currently is not being built as a module by anyone. > > > > Lets remove the couple traces of modularity so that when reading the > > driver there is no doubt it is builtin-only. > > > > Lets remove the modular code that is essentially orphaned, so that > > when reading the driver there is no doubt it is builtin-only. > > [...] > > -MODULE_DESCRIPTION("Exynos Audio Subsystem Clock Controller"); > > -MODULE_LICENSE("GPL v2"); > > -MODULE_ALIAS("platform:exynos-audss-clk"); > > Why not removing .remove() callback as well? > > I don't find sysfs unbind hook useful except testing the exit paths... > which in that case do not exist anymore (there is no "modprobe -r" for > it anyway). Yes, I normally delete the .remove callbacks as indicated in the 0/10, but somehow I overlooked this one. Thanks for spotting it. I'll delete it and disable the sysfs bind in v2. Paul. -- > > Best regards, > Krzysztof >