This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Sun May 12 23:53:33 2024 >From spaans Fri May 29 03:01:05 2015 Received: from pop.ziggo.nl [212.54.42.19] by squeeze.vs19.net with POP3 (fetchmail-6.3.21) for (single-drop); Fri, 29 May 2015 03:01:05 +0200 (CEST) Received: from md1.tb.mail.iss.local ([212.54.34.144]) by mc5.tb.mail.iss.local (Dovecot) with LMTP id 3CuvEam3Z1WISgAAh0Kp1A for ; Fri, 29 May 2015 02:50:13 +0200 Received: from mx17.gn.mail.iss.as9143.net ([212.54.34.144]) by md1.tb.mail.iss.local (Dovecot) with LMTP id RT0GEHPxLFUCQAAAP8oO3g ; Fri, 29 May 2015 02:47:02 +0200 Received: from vger.kernel.org ([209.132.180.67]) by mx17.gn.mail.iss.as9143.net with esmtp (Exim 4.82) (envelope-from ) id 1Yy8V2-0002CX-Vo for bmw12-lkml@ziggo.nl; Fri, 29 May 2015 02:50:13 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755238AbbE2AuG (ORCPT ); Thu, 28 May 2015 20:50:06 -0400 Received: from mail1.windriver.com ([147.11.146.13]:64940 "EHLO mail1.windriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932528AbbE2Atl (ORCPT ); Thu, 28 May 2015 20:49:41 -0400 Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail1.windriver.com (8.15.1/8.15.1) with ESMTPS id t4T0msIw029123 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 28 May 2015 17:48:54 -0700 (PDT) Received: from yow-lpgnfs-02.corp.ad.wrs.com (128.224.149.8) by ALA-HCA.corp.ad.wrs.com (147.11.189.40) with Microsoft SMTP Server id 14.3.224.2; Thu, 28 May 2015 17:48:54 -0700 From: Paul Gortmaker To: Cc: Paul Gortmaker , Richard Henderson , Ivan Kokshaysky , Matt Turner , Subject: [PATCH 06/15] alpha: don't use module_init for non-modular core code Date: Thu, 28 May 2015 20:48:04 -0400 Message-Id: <1432860493-23831-7-git-send-email-paul.gortmaker@windriver.com> X-Mailer: git-send-email 2.2.1 In-Reply-To: <1432860493-23831-1-git-send-email-paul.gortmaker@windriver.com> References: <1432860493-23831-1-git-send-email-paul.gortmaker@windriver.com> Mime-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-Id: X-Mailing-List: linux-kernel@vger.kernel.org X-Ziggo-spamsetting: Instelling=Gemiddeld Scorelimiet=14 X-Ziggo-spambar: / X-Ziggo-spamscore: 0.0 X-Ziggo-spamreport: CMAE Analysis: v=2.1 cv=GaK751jL c=1 sm=0 tr=0 a=UK1r566ZdBxH71SXbqIOeA==:17 a=t7CeM3EgAAAA:8 a=VwQbUJbxAAAA:8 a=cIF5Tx0qAAAA:8 a=bLZqKDXHAAAA:8 a=h1PgugrvaO0A:10 a=rWkr9Ua9AAAA:8 a=tOO0nKmCAAAA:8 a=pGLkceISAAAA:8 a=W0vUJOdyAAAA:8 a=oCWGW8sQWjQXxVQrGgAA: X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No The srm console is always built in. It will never be modular, so using module_init as an alias for __initcall is rather misleading. Fix this up now, so that we can relocate module_init from init.h into module.h in the future. If we don't do this, we'd have to add module.h to obviously non-modular code, and that would be a worse thing. Direct use of __initcall is discouraged, vs prioritized ones. Use of device_initcall is consistent with what __initcall maps onto, and hence does not change the init order, making the impact of this change zero. Should someone with real hardware for boot testing want to change it later to arch_initcall or console_initcall, they can do that at a later date. Cc: Richard Henderson Reviewed-by: Richard Henderson Cc: Ivan Kokshaysky Cc: Matt Turner Cc: linux-alpha@vger.kernel.org Signed-off-by: Paul Gortmaker --- arch/alpha/kernel/srmcons.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/alpha/kernel/srmcons.c b/arch/alpha/kernel/srmcons.c index 6f01d9ad7b81..72b59511e59a 100644 --- a/arch/alpha/kernel/srmcons.c +++ b/arch/alpha/kernel/srmcons.c @@ -237,8 +237,7 @@ srmcons_init(void) return -ENODEV; } - -module_init(srmcons_init); +device_initcall(srmcons_init); /* -- 2.2.1 -- 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/