From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Xen Devel <Xen-devel@lists.xensource.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] linux-next: build warning after merge of the final tree (xen tree related)
Date: Thu, 21 Oct 2010 14:39:56 -0700 [thread overview]
Message-ID: <4CC0B32C.8000503@goop.org> (raw)
In-Reply-To: <20101021145326.9f133f40.sfr@canb.auug.org.au>
On 10/20/2010 08:53 PM, Stephen Rothwell wrote:
> Hi Jeremy,
>
> After merging the final tree, today's linux-next build (i386 defconfig)
> produced this warning:
>
> arch/x86/mm/fault.c: In function 'vmalloc_sync_all':
> arch/x86/mm/fault.c:244: warning: assignment makes integer from pointer without a cast
>
> Introduced by commit aef8b70e5c4b7753fc4bf20dbb01e93fc8883027 ("x86: hold
> mm->page_table_lock while doing vmalloc_sync").
This change got merged into tip/master, and it looks like there's
already a fix there for this warning. I've dropped it from my branch.
Thanks,
J
prev parent reply other threads:[~2010-10-21 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 3:53 linux-next: build warning after merge of the final tree (xen tree related) Stephen Rothwell
2010-10-21 21:39 ` Jeremy Fitzhardinge [this message]
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=4CC0B32C.8000503@goop.org \
--to=jeremy@goop.org \
--cc=Xen-devel@lists.xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.