Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760430Ab3GaOVF (ORCPT ); Wed, 31 Jul 2013 10:21:05 -0400 Received: from mail-pa0-f52.google.com ([209.85.220.52]:65339 "EHLO mail-pa0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760400Ab3GaOUz (ORCPT ); Wed, 31 Jul 2013 10:20:55 -0400 From: Viresh Kumar To: rjw@sisk.pl Cc: linaro-kernel@lists.linaro.org, patches@linaro.org, cpufreq@vger.kernel.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, arnd.bergmann@linaro.org, Viresh Kumar , Kukjin Kim Subject: [PATCH 10/15] cpufreq: s3c24xx: initialize .owner field with THIS_MODULE Date: Wed, 31 Jul 2013 19:49:19 +0530 Message-Id: <08ebac0313328bb7f9701417920e6668861d98be.1375279948.git.viresh.kumar@linaro.org> X-Mailer: git-send-email 1.7.12.rc2.18.g61b472e In-Reply-To: References: In-Reply-To: References: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1207 Lines: 36 CPUFreq core does following at multiple places: module_{get|put}(cpufreq_driver->owner)). This is done to make sure module doesn't get unloaded if it is currently in use. This will work only if the .owner field of cpufreq driver is initialized with a valid pointer. This field wasn't initialized for this driver, lets initialize it with THIS_MODULE. Cc: Kukjin Kim Signed-off-by: Viresh Kumar --- drivers/cpufreq/s3c24xx-cpufreq.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/cpufreq/s3c24xx-cpufreq.c b/drivers/cpufreq/s3c24xx-cpufreq.c index 87781eb..c5a46cc 100644 --- a/drivers/cpufreq/s3c24xx-cpufreq.c +++ b/drivers/cpufreq/s3c24xx-cpufreq.c @@ -479,6 +479,7 @@ static struct cpufreq_driver s3c24xx_driver = { .init = s3c_cpufreq_init, .suspend = s3c_cpufreq_suspend, .resume = s3c_cpufreq_resume, + .owner = THIS_MODULE, .name = "s3c24xx", }; -- 1.7.12.rc2.18.g61b472e -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/