From: Tejun Heo <tj@kernel.org>
To: torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, Lee.Schermerhorn@hp.com,
cl@linux-foundation.org, mingo@elte.hu, adobriyan@gmail.com,
tglx@linutronix.de, hpa@zytor.com, yi.zhu@intel.com,
reinette.chatre@intel.com, ilw@linux.intel.com
Subject: [PATCHSET] remove implicit slab.h inclusion from from percpu.h
Date: Wed, 24 Mar 2010 17:48:54 +0900 [thread overview]
Message-ID: <1269420538-18039-1-git-send-email-tj@kernel.org> (raw)
Hello,
This is the proper patchset to break implicit slab.h inclusion from
percpu.h. Please refer to the last RFC posting[L] for background.
This patchset contains the following four patches.
0001-x86-don-t-include-slab.h-from-arch-x86-include-asm-p.patch
0002-iwlwifi-don-t-include-iwl-dev.h-from-iwl-devtrace.h.patch
0003-include-cleanup-Update-gfp.h-and-slab.h-includes-to-.patch
0004-percpu-don-t-implicitly-include-slab.h-from-percpu.h.patch
0001 and 0002 massages slightly weird inclusion problems in
preparation of further changes.
0003 updates gfp.h and slab.h inclusions such that actual users
include them explicitly. This patch is largely based on conversions
automatically generated by the following script.
http://userweb.kernel.org/~tj/misc/slabh-sweep.py
The patch description explains how the conversion was done and
verified. Please read it for details. This patch was too large
(>1.7M) and only the patch description and diffstat are posted. The
whole patch is available in the git tree or via http[1].
0004 actually updates percpu.h such that slab.h is not included
implicitly.
The following configurations have been tested (more details in patch
0003 description),
* x86 and x86_64 UP and SMP allmodconfig and a custom test config.
* powerpc and powerpc64 SMP allmodconfig
* sparc and sparc64 SMP allmodconfig
* ia64 SMP allmodconfig
* s390 SMP allmodconfig
* alpha SMP allmodconfig
* um on x86_64 SMP allmodconfig
I had only a couple of problems with the above tests and I'm fairly
confident about the coverage of the conversion and if there are
prolems, they are likely to be in arch headers which should be easy to
discover and fix on most builds of the affected arch.
If nobody objects, I'd like to publish it to linux-next through the
percpu tree, let it settle and get tested there for some time. Ingo,
it would also be great if you can put these changes through your build
tests.
After it gets some testing, if Linus agrees, I hope this could be
pulled into the mainline although the merge window is well over now.
The changes are mostly trivial and I actually think it makes more
sense to merge this kind of stuff while the code base is relatively
stable.
The patchset is available in the following git branch.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git slabh
and the patch tarball at
http://userweb.kernel.org/~tj/patches/slabh.tar.gz
Thanks.
--
tejun
[L] http://thread.gmane.org/gmane.linux.kernel/960180
[1] http://userweb.kernel.org/~tj/patches/0003-include-cleanup-Update-gfp.h-and-slab.h-includes-to-.patch
next reply other threads:[~2010-03-24 8:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 8:48 Tejun Heo [this message]
2010-03-24 8:48 ` [PATCH 1/4] x86: don't include slab.h from arch/x86/include/asm/pgtable_32.h Tejun Heo
2010-03-24 10:58 ` Pekka Enberg
2010-03-24 19:43 ` Christoph Lameter
2010-03-24 8:48 ` [PATCH 2/4] iwlwifi: don't include iwl-dev.h from iwl-devtrace.h Tejun Heo
2010-03-24 17:55 ` reinette chatre
2010-03-24 8:48 ` [PATCH 3/4] include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h Tejun Heo
2010-03-24 11:00 ` Pekka Enberg
2010-03-24 11:57 ` Alexey Dobriyan
2010-03-24 13:33 ` Tejun Heo
2010-03-24 19:42 ` Christoph Lameter
2010-03-30 14:30 ` Lee Schermerhorn
2010-03-31 2:41 ` Tejun Heo
2010-03-24 8:48 ` [PATCH 4/4] percpu: don't implicitly include slab.h " Tejun Heo
2010-03-24 19:23 ` Christoph Lameter
2010-03-29 0:50 ` [PATCHSET] remove implicit slab.h inclusion from " Tejun Heo
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=1269420538-18039-1-git-send-email-tj@kernel.org \
--to=tj@kernel.org \
--cc=Lee.Schermerhorn@hp.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=ilw@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=reinette.chatre@intel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=yi.zhu@intel.com \
/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