public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Fix implicit <module.h> users that will break later.
Date: Tue, 30 Jun 2015 03:32:24 -0400	[thread overview]
Message-ID: <20150630073224.GD8349@windriver.com> (raw)

The files changed here are simply modular source files that are implicitly
relying on <module.h> being present.  We fix them up now, so that we can
decouple some of the module related init code from the core init code in
the future.

The addition of the module.h include to several files here is also a
no-op from a code generation point of view, else there would already be
compile issues with these files today.

There may be lots more implicit includes of <module.h> in tree, but
these are the ones that extensive build test coverage has shown that
must be fixed in order to avoid build breakage fallout for the
pending module.h <---> init.h code relocation we desire to complete.

Original posting:
  "Fix implicit includes of <module.h> that will break."
  https://lkml.kernel.org/r/1430444867-22342-1-git-send-email-paul.gortmaker@windriver.com

Thanks,
Paul.
---

The following changes since commit 0f57d86787d8b1076ea8f9cbdddda2a46d534a27:

  Linux 4.1-rc8 (2015-06-14 15:51:10 -1000)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux.git tags/module-implicit-v4.1-rc8

for you to fetch changes up to 7cac34370a4dde12e6430c2f0985926d4ef0f459:

  frv: add module.h to mb93090-mb00/flash.c to avoid compile fail (2015-06-16 14:12:26 -0400)

----------------------------------------------------------------
Fix up implicit <module.h> users that will break later.

----------------------------------------------------------------
Paul Gortmaker (11):
      drivers/clk: include <module.h> for clk-max77xxx modular code
      drivers/gpio: include <module.h> for modular crystalcove code
      drivers/gpu: include <module.h> for modular rockchip code
      drivers/hsi: include <module.h> for modular omap_ssi code
      drivers/pcmcia: include <module.h> for modular xxs1500_ss code
      drivers/regulator: include <module.h> for modular max77802 code
      sh: mach-highlander/psw.c is tristate and should use module.h
      crypto/asymmetric_keys: pkcs7_key_type needs module.h
      drivers/staging: include <module.h> for modular android tegra_ion code
      drivers/cpufreq: include <module.h> for modular exynos-cpufreq.c code
      frv: add module.h to mb93090-mb00/flash.c to avoid compile fail

 arch/frv/mb93090-mb00/flash.c                 | 2 +-
 arch/sh/boards/mach-highlander/psw.c          | 2 +-
 crypto/asymmetric_keys/pkcs7_key_type.c       | 1 +
 drivers/clk/clk-max77686.c                    | 1 +
 drivers/clk/clk-max77802.c                    | 1 +
 drivers/cpufreq/exynos-cpufreq.c              | 1 +
 drivers/gpio/gpio-crystalcove.c               | 1 +
 drivers/gpu/drm/rockchip/rockchip_drm_drv.c   | 1 +
 drivers/gpu/drm/rockchip/rockchip_drm_vop.c   | 1 +
 drivers/hsi/controllers/omap_ssi.h            | 1 +
 drivers/pcmcia/xxs1500_ss.c                   | 1 +
 drivers/regulator/max77802.c                  | 1 +
 drivers/staging/android/ion/tegra/tegra_ion.c | 1 +
 13 files changed, 13 insertions(+), 2 deletions(-)

                 reply	other threads:[~2015-06-30  7:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20150630073224.GD8349@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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