From mboxrd@z Thu Jan 1 00:00:00 1970 From: Viresh Kumar Subject: Re: [PATCH v2] cpufreq: qcom-kryo: Fix section mismatch warning Date: Thu, 20 Sep 2018 09:02:45 -0700 Message-ID: <20180920160245.f4afwfyyz3nd4xvn@vireshk-mac-ubuntu> References: <20180919182247.1101-1-natechancellor@gmail.com> <20180919215039.mb7prmmfs5jek3aj@vireshk-mac-ubuntu> <20180919215418.y2jsrsj73vy3dudd@vireshk-mac-ubuntu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: "Rafael J. Wysocki" Cc: ndesaulniers@google.com, natechancellor@gmail.com, ilia.lin@gmail.com, "Rafael J. Wysocki" , Linux PM , Linux Kernel Mailing List List-Id: linux-pm@vger.kernel.org On 20-09-18, 00:45, Rafael J. Wysocki wrote: > Because __init things go away at one point and calling them from the > other sections is a bad idea. OTOH, __exit things are simply not > needed in built-in drivers and they are never there if the driver is > built-in, so calling them from the other sections is a bad idea too. I assumed that the driver is calling platform_driver_probe() and so probe() can be marked __init. But it doesn't do that to make deferred probing work. -- viresh