Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754782AbaFJF32 (ORCPT ); Tue, 10 Jun 2014 01:29:28 -0400 Received: from mail-ob0-f178.google.com ([209.85.214.178]:63782 "EHLO mail-ob0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751113AbaFJF30 (ORCPT ); Tue, 10 Jun 2014 01:29:26 -0400 MIME-Version: 1.0 In-Reply-To: <53962087.8000706@semaphore.gr> References: <53962087.8000706@semaphore.gr> Date: Tue, 10 Jun 2014 10:59:25 +0530 Message-ID: Subject: Re: [PATCH 5/7] cpufreq: intel_pstate: Remove redundant includes From: Viresh Kumar To: Stratos Karafotis Cc: "Rafael J. Wysocki" , Dirk Brandewie , "linux-pm@vger.kernel.org" , LKML Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10 June 2014 02:30, Stratos Karafotis wrote: > Also put them in alphabetical order. > > Signed-off-by: Stratos Karafotis > --- > drivers/cpufreq/intel_pstate.c | 17 ++--------------- > 1 file changed, 2 insertions(+), 15 deletions(-) > > diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c > index 26a0262..d4f0518 100644 > --- a/drivers/cpufreq/intel_pstate.c > +++ b/drivers/cpufreq/intel_pstate.c > @@ -10,26 +10,13 @@ > * of the License. > */ > > -#include > -#include > -#include > -#include > -#include > -#include > -#include > -#include > -#include > +#include > #include > #include > -#include > -#include > -#include > #include > -#include > +#include > #include > > -#include > -#include > #include As a rule, header files for all the symbols directly used by a file must be included directly by the file and must not depend on indirect inclusions. So even if it compiles, its the wrong thing to do. Though you can obviously remove the headers which aren't used. -- 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/