From: Andrew Morton <akpm@linux-foundation.org>
To: Daniel Cashman <dcashman@google.com>
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: Fri, 4 Dec 2015 17:01:13 -0800 [thread overview]
Message-ID: <20151204170113.c5cd8a9cc9658c491851bc33@linux-foundation.org> (raw)
In-Reply-To: <CAJQetW4L6Zuzd9GENK6XMg+OVtFUjyE4jOzoG+VB3HtwmoUmiA@mail.gmail.com>
On Fri, 4 Dec 2015 16:56:19 -0800 Daniel Cashman <dcashman@google.com> wrote:
> I've left the question of whether or not
> the value should be the number of randomized bits (current situation)
> or the size of the address space chunk affected up to akpm@.
Does it matter much? It can always be changed later if it proves to be
a problem.
> 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?
--
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>
next prev parent reply other threads:[~2015-12-05 1:01 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 [this message]
2015-12-05 1:46 ` Daniel Cashman
2015-12-07 18:13 ` Daniel Cashman
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=20151204170113.c5cd8a9cc9658c491851bc33@linux-foundation.org \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).