Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753923AbaAVA1C (ORCPT ); Tue, 21 Jan 2014 19:27:02 -0500 Received: from ozlabs.org ([203.10.76.45]:45298 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752872AbaAVA06 (ORCPT ); Tue, 21 Jan 2014 19:26:58 -0500 From: Rusty Russell To: Paul Gortmaker , linux-kernel@vger.kernel.org Cc: linux-arch@vger.kernel.org, Paul Gortmaker Subject: Re: [PATCH 31/73] module: relocate module_init from init.h to module.h In-Reply-To: <1390339396-3479-32-git-send-email-paul.gortmaker@windriver.com> References: <1390339396-3479-1-git-send-email-paul.gortmaker@windriver.com> <1390339396-3479-32-git-send-email-paul.gortmaker@windriver.com> User-Agent: Notmuch/0.15.2 (http://notmuchmail.org) Emacs/23.4.1 (x86_64-pc-linux-gnu) Date: Wed, 22 Jan 2014 10:46:06 +1030 Message-ID: <87ha8w50s9.fsf@rustcorp.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Paul Gortmaker writes: > Modular users will always be users of init functionality, but > users of init functionality are not necessarily always modules. > > Hence any functionality like module_init and module_exit would > be more at home in the module.h file. And module.h should > explicitly include init.h to make the dependency clear. > > We've already done all the legwork needed to ensure that this > move does not cause any build regressions due to implicit > header file include assumptions about where module_init lives. > > Cc: Rusty Russell > Signed-off-by: Paul Gortmaker Acked-by: Rusty Russell Want to delete the extraneous semicolons, for bonus points? :) > +#define module_init(x) __initcall(x); ... > +#define module_exit(x) __exitcall(x); Cheers, Rusty. -- 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/