From: Tejun Heo <tj@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL linux-next] break implicit percpu.h -> slab.h dependency
Date: Mon, 29 Mar 2010 10:00:44 +0900 [thread overview]
Message-ID: <4BAFFBBC.5040402@kernel.org> (raw)
Hello, Stephen.
Can you please pull the following into linux-next?
git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git slabh
The tree breaks implicit slab.h inclusion from percpu.h. It turned
out that a lot of .c files assumed slab/gfp availability w/o actually
including the respective header, so the conversion ended up modifying
includes on over 4000 files.
I don't expect there to be a lot of conflicts and the ones which
happen should be straight forward to resolve. Albeit large in volume,
the changes being mostly trivial, I'm hoping to push this into Linus
tree soonish (ie. during this devel cycle), so the tree hopefully will
go away soon.
Please read the following thread for details.
http://thread.gmane.org/gmane.linux.kernel/965549
Thank you.
--
tejun
next reply other threads:[~2010-03-29 1:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 1:00 Tejun Heo [this message]
2010-03-29 12:21 ` [GIT PULL linux-next] break implicit percpu.h -> slab.h dependency Stephen Rothwell
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=4BAFFBBC.5040402@kernel.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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