From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mark Salter <msalter@redhat.com>,
linux-next@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
ccross@android.com
Subject: Re: linux-next build failure
Date: Wed, 30 Oct 2013 13:50:42 -0700 [thread overview]
Message-ID: <20131030135042.9c40bca11370c2cfef29ff51@linux-foundation.org> (raw)
In-Reply-To: <20131031073700.f9642ce6c35674a45b3905bc@canb.auug.org.au>
On Thu, 31 Oct 2013 07:37:00 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> [Jut add Andrew to the cc list]
>
> On Wed, 30 Oct 2013 11:27:45 -0400 Mark Salter <msalter@redhat.com> wrote:
> >
> > This patch causes a build failure for no-MMU builds:
> >
> > commit 41df2957cb010edfa2f9d394d3617da6beeeb660
> > Author: Colin Cross <ccross@android.com>
> > Date: Wed Oct 30 11:45:39 2013 +1100
> >
> > mm: add a field to store names for private anonymous memory
> >
> > The problem is:
> >
> > kernel/built-in.o: In function `sys_prctl':
> > (.text+0x19854): undefined reference to `madvise_set_anon_name'
> >
> > madvise doesn't make sense without an MMU.
> >
> > --Mark
OK, thanks. I'll drop
mm-rearrange-madvise-code-to-allow-for-reuse.patch
mm-add-a-field-to-store-names-for-private-anonymous-memory.patch
mm-add-a-field-to-store-names-for-private-anonymous-memory-fix.patch
mm-add-a-field-to-store-names-for-private-anonymous-memory-fix-fix-2.patch
for now. They have other question marks - let's revisit everything
after 3.13-rc1.
next prev parent reply other threads:[~2013-10-30 20:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 15:27 Mark Salter
2013-10-30 20:37 ` Stephen Rothwell
2013-10-30 20:50 ` Andrew Morton [this message]
2013-10-30 23:17 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2013-11-08 16:51 Mark Salter
2008-10-20 12:04 linux-next: " Stephen Rothwell
2008-10-20 15:48 ` Greg KH
2008-10-20 16:33 ` J.R. Mauro
2008-10-20 16:51 ` Greg KH
2008-10-20 20:47 ` Greg KH
2008-10-20 22:34 ` J.R. Mauro
2008-10-20 22:31 ` Stephen Rothwell
2008-08-25 11:28 Stephen Rothwell
2008-08-25 12:40 ` Ingo Molnar
2008-08-28 7:40 ` David Miller
2008-07-29 6:23 Stephen Rothwell
2008-07-29 8:00 ` Ingo Molnar
2008-07-29 8:03 ` Stephen Rothwell
2008-07-29 8:58 ` Ingo Molnar
2008-07-29 11:28 ` KOSAKI Motohiro
2008-07-29 11:40 ` Ingo Molnar
2008-07-29 14:31 ` Mike Travis
2008-07-29 14:33 ` Mike Travis
2008-07-29 16:33 ` Linus Torvalds
2008-07-29 16:42 ` Ingo Molnar
2008-07-29 16:44 ` Linus Torvalds
2008-07-29 8:14 ` Wenji Huang
2008-07-29 16:26 ` Linus Torvalds
2008-07-28 5:07 Stephen Rothwell
2008-07-28 4:44 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=20131030135042.9c40bca11370c2cfef29ff51@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ccross@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=msalter@redhat.com \
--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
all inboxes | Powered by JetHome®