From: Daniel Cashman <dcashman@android.com>
To: Daniel Cashman <dcashman@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild test robot <fengguang.wu@intel.com>,
kbuild-all@01.org, Mark Brown <broonie@kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 4174/4356] kernel/built-in.o:undefined reference to `mmap_rnd_bits'
Date: Mon, 7 Dec 2015 10:13:46 -0800 [thread overview]
Message-ID: <5665CC5A.7030407@android.com> (raw)
In-Reply-To: <CAJQetW54FNRKd5LtpkAk0P_bPyAZi6iKnZhEhz1n9oSOm-Wc9Q@mail.gmail.com>
On 12/04/2015 05:46 PM, Daniel Cashman wrote:
>>> Please let me know what else should be done in v6 to keep these in.
>>
>> It sounds like all we need to do at present is to fix this build error?
>
> My apologies, I thought this was the one related to CONFIG_MMU=n.
> I've reproduced locally and will look into this on Monday.
>
Actually, I just cloned linux-next and am not seeing this when
cross-compiling arm with the provided config unless "if MMU" is removed.
So perhaps it was the same error and my local state was strange?
At present, I plan to prepare v6 to make some minor arm64 Kconfig
changes and corrects the ifdef missing character.
Thank You,
Dan
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2015-12-07 18:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 16:18 [linux-next:master 4174/4356] kernel/built-in.o:undefined reference to `mmap_rnd_bits' kbuild test robot
2015-12-04 23:14 ` Andrew Morton
2015-12-04 23:19 ` Andrew Morton
2015-12-05 0:56 ` Daniel Cashman
2015-12-05 1:01 ` Andrew Morton
2015-12-05 1:46 ` Daniel Cashman
2015-12-07 18:13 ` Daniel Cashman [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=5665CC5A.7030407@android.com \
--to=dcashman@android.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=dcashman@google.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
/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.