linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jason Cooper <jason@lakedaemon.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild test robot <fengguang.wu@intel.com>,
	kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [mmotm:master 70/106] arch/x86/kernel/process.c:511:9: error: implicit declaration of function 'randomize_page'
Date: Mon, 15 Aug 2016 22:31:24 +0000	[thread overview]
Message-ID: <20160815223124.GN3353@io.lakedaemon.net> (raw)
In-Reply-To: <20160815144607.1a6c05709668b3ecd61e55da@linux-foundation.org>

On Mon, Aug 15, 2016 at 02:46:07PM -0700, Andrew Morton wrote:
> On Thu, 11 Aug 2016 21:31:15 -0400 Jason Cooper <jason@lakedaemon.net> wrote:
> > I think you have v1 and v2 of the randomize page patches in your stack. Could you drop v1 please?

I was wrong here.  The patches are mis-labelled.  The patches labelled
'v2' are deltas regressing to an older version of the series.

> I have the v1 series and a series of deltas which turn that into v2.
> 
> I also see a v3 on the lists so I'm all confused.  Please triple-check
> linux-next versus your latest version.

This is currently in akpm/next:

  9f60fb9385f5 random: remove unused randomize_range()
  81221b53ea05 unicore32-use-simpler-api-for-random-address-requests-v2
  6205f3d87280 unicore32: use simpler API for random address requests
  af8c36a0a66a tile-use-simpler-api-for-random-address-requests-v2
  18c80b9aa3a3 tile: use simpler API for random address requests
  742fffc5251b arm64-use-simpler-api-for-random-address-requests-v2
  f30c92be8d31 arm64: use simpler API for random address requests
  cbcb520687fd arm-use-simpler-api-for-random-address-requests-v2
  f39cdf6eca33 ARM: use simpler API for random address requests
  2f20ec82da2e x86-use-simpler-api-for-random-address-requests-v2
  c8923c663214 x86: use simpler API for random address requests
  027cac3e28bd random-simplify-api-for-random-address-requests-v2
  b990c09770d3 random: simplify API for random address requests

if you remove the patches that match /random-address-requests-v2$/, then
things should be good.  I've confirmed that

  b990c09770d3 random: simplify API for random address requests

is the proper version and that every other patch on top of that
correctly adds randomize_page().  It's the ones labelled 'v2' that are
reverting changes to an older version of the series (randomize_addr).

> I can't reproduced this build error.

It's a build failure that only occurs when a bisect would land in the
middle of the old series.  Removing the patches labelled v2 should fix
it.

Sorry for the confusion.

thx,

Jason.

--
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>

      reply	other threads:[~2016-08-15 22:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-12  1:19 kbuild test robot
2016-08-12  1:31 ` Jason Cooper
2016-08-15 21:46   ` Andrew Morton
2016-08-15 22:31     ` Jason Cooper [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=20160815223124.GN3353@io.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=hannes@cmpxchg.org \
    --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