From: Jan Kiszka <jan.kiszka@web.de>
To: Tejun Heo <tj@kernel.org>
Cc: Jeff Dike <jdike@addtoit.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
user-mode-linux-devel@lists.sourceforge.net,
Tiger Yang <tiger.yang@oracle.com>
Subject: Re: [PATCH] uml: Fix build breakage after slab.h changes
Date: Mon, 19 Apr 2010 09:35:28 +0200 [thread overview]
Message-ID: <4BCC07C0.5050601@web.de> (raw)
In-Reply-To: <4BCB788E.2040501@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
Tejun Heo wrote:
> Hello,
>
> On 04/19/2010 01:37 AM, Jan Kiszka wrote:
>> We now have to to include linux/slab.h explicitly for kmalloc & friends.
>> Files that build against host headers already get their prototypes via
>> um_malloc.h, linux/slab.h may even be unavailable.
>
> Hmmm... my test um build was okay but I don't know much about details
> of um builds.
We may use different configs. Also, your userland includes have to lack
slab.h.
> I suppose this patch will go through um tree?
Good question. Does such a tree exist? I'm sitting on a few more um
cleanups & fixes, and so far I'm working against Linus' tree as I failed
to find anything more recent.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2010-04-19 7:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 16:37 Jan Kiszka
2010-04-18 21:24 ` Tejun Heo
2010-04-19 7:35 ` Jan Kiszka [this message]
2010-04-19 8:19 ` Tejun Heo
2010-04-19 16:29 ` Jiri Kosina
2010-04-19 20:10 ` Jan Kiszka
2010-04-19 20:12 ` Jiri Kosina
2010-04-20 14:31 ` Jeff Dike
2010-04-20 17:11 ` Jan Kiszka
2010-04-19 8:51 ` 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=4BCC07C0.5050601@web.de \
--to=jan.kiszka@web.de \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tiger.yang@oracle.com \
--cc=tj@kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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