From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>, <rusty@rustcorp.com.au>
Subject: [GIT PULL] Fixup code that is fragile wrt init.h code moving to module.h
Date: Tue, 30 Jun 2015 21:30:47 -0400 [thread overview]
Message-ID: <20150701013047.GD8621@windriver.com> (raw)
What started as a removal of no longer required include <linux/init.h>
due to the earlier __cpuinit and __devinit removal led to the observation
that some module specfic support was living in init.h itself, thus
preventing the full removal from introducing compile regressions.
This series of commits includes a few final fixups needed prior to the
relocation of the modular init code from <init.h> to <module.h>.
These are things that weren't easily categorized into any of the other
previous series categories already requested for pull.
That said, each fixup branch (including this one) is independent and
there are no ordering constraints. Only the final code relocation
(which is NOT in this pull) at the top here:
http://git.kernel.org/cgit/linux/kernel/git/paulg/linux.git/log/?h=init-v4.1-rc8
requires that all my cleanup branches be merged 1st. This is what is
above, and what we used for linux-next testing; merge all the cleanups
_then_ apply the move. All possible care has been taken to avoid
introducing any bisect build fails into our history with all of this
work, including how it gets integrated into mainline.
The final move commit can come in whatever way suits; from me against
v4.2-rc1, taken by you from the above; via Rusty's module tree post 4.2-rc1?
Original posting:
https://lkml.kernel.org/r/1433276168-21550-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-misc-v4.1-rc8
for you to fetch changes up to 32e805e7c6a343894c95a3431973e8ddad4aa2cf:
tile: add init.h to usb.c to avoid compile failure (2015-06-16 14:12:41 -0400)
----------------------------------------------------------------
Fixup various init.h misuses that are fragile wrt code moving to module.h
----------------------------------------------------------------
Paul Gortmaker (3):
x86: replace __init_or_module with __init in non-modular vsmp_64.c
arm: fix implicit #include <linux/init.h> in entry asm.
tile: add init.h to usb.c to avoid compile failure
arch/arm/kernel/entry-armv.S | 2 ++
arch/tile/kernel/usb.c | 1 +
arch/x86/kernel/vsmp_64.c | 2 +-
3 files changed, 4 insertions(+), 1 deletion(-)
reply other threads:[~2015-07-01 1:31 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=20150701013047.GD8621@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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