This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Sat Apr 27 06:53:58 2024 Envelope-to: j@jasper.es Delivery-date: Tue, 21 Jan 2014 22:59:54 +0100 Received: from localhost ([127.0.0.1] helo=squeeze.vs19.net) by squeeze.vs19.net with esmtp (Exim 4.80) (envelope-from ) id 1W5jMO-0001oQ-Ln for j@jasper.es; Tue, 21 Jan 2014 22:59:53 +0100 Original-Recipient: rfc822;jasper@telfort.nl Received: from pop3.telfort.nl [213.75.3.52] by squeeze.vs19.net with POP3 (fetchmail-6.3.21) for (single-drop); Tue, 21 Jan 2014 22:59:52 +0100 (CET) Received: from cpxmta-msg01.kpnxchange.com (10.94.114.22) by cpxmbs-msg01.support.local (8.6.060.31) id 52B0AB3D01883AC3 for jasper@telfort.nl; Tue, 21 Jan 2014 22:44:59 +0100 Received: from cpsmtpb-ews09.kpnxchange.com (213.75.39.14) by cpxmta-msg01.kpnxchange.com (8.6.060.14) id 5279B8F408C60F40 for jasper@telfort.nl; Tue, 21 Jan 2014 22:44:59 +0100 Received: from cpsps-ews30.kpnxchange.com ([10.94.84.196]) by cpsmtpb-ews09.kpnxchange.com with Microsoft SMTPSVC(7.5.7601.17514); Tue, 21 Jan 2014 22:44:59 +0100 Received: from vger.kernel.org ([209.132.180.67]) by cpsps-ews30.kpnxchange.com with Microsoft SMTPSVC(7.5.7601.17514); Tue, 21 Jan 2014 22:44:59 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932211AbaAUVot (ORCPT ); Tue, 21 Jan 2014 16:44:49 -0500 Received: from mail.windriver.com ([147.11.1.11]:56297 "EHLO mail.windriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754340AbaAUVYp (ORCPT ); Tue, 21 Jan 2014 16:24:45 -0500 Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail.windriver.com (8.14.5/8.14.5) with ESMTP id s0LLOav8023743 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 21 Jan 2014 13:24:37 -0800 (PST) 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.2.347.0; Tue, 21 Jan 2014 13:24:36 -0800 From: Paul Gortmaker To: Cc: , Paul Gortmaker , Richard Henderson , Ivan Kokshaysky , Matt Turner , Subject: [PATCH 22/73] alpha: don't use module_init for non-modular core code Date: Tue, 21 Jan 2014 16:22:25 -0500 Message-Id: <1390339396-3479-23-git-send-email-paul.gortmaker@windriver.com> X-Mailer: git-send-email 1.8.4.1 In-Reply-To: <1390339396-3479-1-git-send-email-paul.gortmaker@windriver.com> References: <1390339396-3479-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-OriginalArrivalTime: 21 Jan 2014 21:44:59.0196 (UTC) FILETIME=[082AE7C0:01CF16F2] X-RcptDomain: telfort.nl 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 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 6f01d9a..72b5951 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); /* -- 1.8.4.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/