Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752674Ab3HCLwK (ORCPT ); Sat, 3 Aug 2013 07:52:10 -0400 Received: from mail-ob0-f173.google.com ([209.85.214.173]:60102 "EHLO mail-ob0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752338Ab3HCLuv (ORCPT ); Sat, 3 Aug 2013 07:50:51 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Sat, 3 Aug 2013 17:20:50 +0530 Message-ID: Subject: Re: [PATCH 00/15] cpufreq: initialize drivers .owner field with THIS_MODULE 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 Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 855 Lines: 20 On 31 July 2013 19:49, Viresh Kumar wrote: > 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 many cpufreq driver, lets initialize it with > THIS_MODULE. You can drop this patchset now as .owner field is removed in the latest patchset from me which is posted today: "[PATCH 00/10] CPUFreq: Fixes & Cleanups for 3.12" -- 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/