mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Russell King <linux@arm.linux.org.uk>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: [PATCH 0/3] arm: remap non-modular uses of module_init properly
Date: Mon, 13 Jan 2014 19:19:40 -0500	[thread overview]
Message-ID: <1389658783-9876-1-git-send-email-paul.gortmaker@windriver.com> (raw)

The goal is to move module_init/module_exit from init.h and into
module.h -- however in doing so, we uncover several instances in
ARM code where module_init is used somewhat incorrectly by non modular
code, and a file that needs module.h but isn't sourcing it.  We need to
make these fixups 1st before changing the headers so that we don't cause
build failures later on.

The changes are largely inert, however we do cause a largely trivial
change in one initcall ordering -- that happens because module_init
is really device_initcall; but I didn't use device_initcall because
subsys_initcall seems somewhat more appropriate.

All modified files were build tested on today's linux next tree.

Paul.
---

Paul Gortmaker (3):
  arm: use subsys_initcall in non-modular pl320 IPC code
  arm: include module.h in drivers/bus/omap_l3_smx.c
  arm: don't use module_init in non-modular mach-vexpress/spc.c code

 arch/arm/mach-vexpress/spc.c | 2 +-
 drivers/bus/omap_l3_smx.c    | 1 +
 drivers/mailbox/pl320-ipc.c  | 2 +-
 3 files changed, 3 insertions(+), 2 deletions(-)

-- 
1.8.5.2


             reply	other threads:[~2014-01-14  0:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14  0:19 Paul Gortmaker [this message]
2014-01-14  0:19 ` [PATCH 1/3] arm: use subsys_initcall in non-modular pl320 IPC code Paul Gortmaker
2014-01-14  0:19 ` [PATCH 2/3] arm: include module.h in drivers/bus/omap_l3_smx.c Paul Gortmaker
2014-01-14  0:19 ` [PATCH 3/3] arm: don't use module_init in non-modular mach-vexpress/spc.c code Paul Gortmaker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1389658783-9876-1-git-send-email-paul.gortmaker@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome