From: Nathan Zimmer <nzimmer@sgi.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the final tree
Date: Thu, 2 Aug 2012 09:45:50 -0500 [thread overview]
Message-ID: <501A929E.5020000@sgi.com> (raw)
In-Reply-To: <20120802140428.f045d5eb03bd2a5e03a5230d@canb.auug.org.au>
On 08/01/2012 11:04 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (sparc64 defconfig)
> produced this warning:
>
> mm/shmem.c: In function 'shmem_interleave':
> mm/shmem.c:1343:9: warning: assignment makes integer from pointer without a cast [enabled by default]
>
> Introduced by commit c3cfa3129c03 ("tmpfs: interleave the starting node
> of /dev/shmem") from the akpm tree.
>
That should disappear shortly. The patch responsible was obsoleted.
Nate
WARNING: multiple messages have this Message-ID (diff)
From: Nathan Zimmer <nzimmer@sgi.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
<linux-next@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the final tree
Date: Thu, 2 Aug 2012 09:45:50 -0500 [thread overview]
Message-ID: <501A929E.5020000@sgi.com> (raw)
In-Reply-To: <20120802140428.f045d5eb03bd2a5e03a5230d@canb.auug.org.au>
On 08/01/2012 11:04 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (sparc64 defconfig)
> produced this warning:
>
> mm/shmem.c: In function 'shmem_interleave':
> mm/shmem.c:1343:9: warning: assignment makes integer from pointer without a cast [enabled by default]
>
> Introduced by commit c3cfa3129c03 ("tmpfs: interleave the starting node
> of /dev/shmem") from the akpm tree.
>
That should disappear shortly. The patch responsible was obsoleted.
Nate
next prev parent reply other threads:[~2012-08-02 14:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 4:04 linux-next: build warning after merge of the final tree Stephen Rothwell
2012-08-02 14:45 ` Nathan Zimmer [this message]
2012-08-02 14:45 ` Nathan Zimmer
-- strict thread matches above, loose matches on Subject: below --
2013-05-29 5:29 Stephen Rothwell
2013-05-29 5:29 ` Stephen Rothwell
2013-05-29 5:44 ` David Miller
2013-04-19 8:07 Stephen Rothwell
2013-04-19 9:44 ` Joerg Roedel
2012-12-17 3:22 Stephen Rothwell
2012-12-17 3:22 ` Stephen Rothwell
2012-12-17 3:34 ` Stephen Rothwell
2012-12-17 3:34 ` Stephen Rothwell
2012-12-17 3:34 ` Stephen Rothwell
2012-12-17 20:59 ` Andrew Morton
2012-12-17 20:59 ` Andrew Morton
2012-12-17 20:59 ` Andrew Morton
2012-03-26 4:11 Stephen Rothwell
2012-03-28 7:59 ` Williams, Dan J
2011-08-16 5:22 Stephen Rothwell
2011-08-16 5:22 ` Stephen Rothwell
2011-08-16 6:04 ` Herbert Xu
2011-08-16 6:04 ` Herbert Xu
2011-08-16 7:03 ` Stephen Rothwell
2011-08-16 7:03 ` Stephen Rothwell
2011-08-16 7:08 ` Herbert Xu
2011-08-16 7:08 ` Herbert Xu
2011-07-22 6:24 Stephen Rothwell
2011-07-22 6:24 ` Stephen Rothwell
2011-07-22 6:26 ` David Miller
2010-09-29 4:02 Stephen Rothwell
2010-09-16 5:05 Stephen Rothwell
2010-09-16 6:29 ` Jens Axboe
2010-05-26 5:15 Stephen Rothwell
2010-05-26 5:15 ` Stephen Rothwell
2010-03-01 8:14 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=501A929E.5020000@sgi.com \
--to=nzimmer@sgi.com \
--cc=akpm@linux-foundation.org \
--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.