All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: akpm@linux-foundation.org, broonie@kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
	mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
	richard -rw- weinberger <richard.weinberger@gmail.com>,
	Eugeniu Rosca <erosca@de.adit-jv.com>
Subject: Re: mmotm 2018-02-21-14-48 uploaded (mm/page_alloc.c on UML)
Date: Wed, 21 Feb 2018 15:58:41 -0800	[thread overview]
Message-ID: <7bcc52db-57eb-45b0-7f20-c93a968599cd@infradead.org> (raw)
In-Reply-To: <20180221224839.MqsDtkGCK%akpm@linux-foundation.org>

On 02/21/2018 02:48 PM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2018-02-21-14-48 has been uploaded to
> 
>    http://www.ozlabs.org/~akpm/mmotm/
> 
> mmotm-readme.txt says
> 
> README for mm-of-the-moment:
> 
> http://www.ozlabs.org/~akpm/mmotm/
> 
> This is a snapshot of my -mm patch queue.  Uploaded at random hopefully
> more than once a week.
> 
> You will need quilt to apply these patches to the latest Linus release (4.x
> or 4.x-rcY).  The series file is in broken-out.tar.gz and is duplicated in
> http://ozlabs.org/~akpm/mmotm/series
> 
> The file broken-out.tar.gz contains two datestamp files: .DATE and
> .DATE-yyyy-mm-dd-hh-mm-ss.  Both contain the string yyyy-mm-dd-hh-mm-ss,
> followed by the base kernel version against which this patch series is to
> be applied.

um (or uml) defconfig on i386 and/or x86_64:

../mm/page_alloc.c: In function 'memmap_init_zone':
../mm/page_alloc.c:5450:5: error: implicit declaration of function 'memblock_next_valid_pfn' [-Werror=implicit-function-declaration]
     pfn = memblock_next_valid_pfn(pfn, end_pfn) - 1;
     ^


probably (?):
From: Eugeniu Rosca <erosca@de.adit-jv.com>
Subject: mm: page_alloc: skip over regions of invalid pfns on UMA


-- 
~Randy

WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <rdunlap@infradead.org>
To: akpm@linux-foundation.org, broonie@kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
	mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
	richard -rw- weinberger <richard.weinberger@gmail.com>,
	Eugeniu Rosca <erosca@de.adit-jv.com>
Subject: Re: mmotm 2018-02-21-14-48 uploaded (mm/page_alloc.c on UML)
Date: Wed, 21 Feb 2018 15:58:41 -0800	[thread overview]
Message-ID: <7bcc52db-57eb-45b0-7f20-c93a968599cd@infradead.org> (raw)
In-Reply-To: <20180221224839.MqsDtkGCK%akpm@linux-foundation.org>

On 02/21/2018 02:48 PM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2018-02-21-14-48 has been uploaded to
> 
>    http://www.ozlabs.org/~akpm/mmotm/
> 
> mmotm-readme.txt says
> 
> README for mm-of-the-moment:
> 
> http://www.ozlabs.org/~akpm/mmotm/
> 
> This is a snapshot of my -mm patch queue.  Uploaded at random hopefully
> more than once a week.
> 
> You will need quilt to apply these patches to the latest Linus release (4.x
> or 4.x-rcY).  The series file is in broken-out.tar.gz and is duplicated in
> http://ozlabs.org/~akpm/mmotm/series
> 
> The file broken-out.tar.gz contains two datestamp files: .DATE and
> .DATE-yyyy-mm-dd-hh-mm-ss.  Both contain the string yyyy-mm-dd-hh-mm-ss,
> followed by the base kernel version against which this patch series is to
> be applied.

um (or uml) defconfig on i386 and/or x86_64:

../mm/page_alloc.c: In function 'memmap_init_zone':
../mm/page_alloc.c:5450:5: error: implicit declaration of function 'memblock_next_valid_pfn' [-Werror=implicit-function-declaration]
     pfn = memblock_next_valid_pfn(pfn, end_pfn) - 1;
     ^


probably (?):
From: Eugeniu Rosca <erosca@de.adit-jv.com>
Subject: mm: page_alloc: skip over regions of invalid pfns on UMA


-- 
~Randy

--
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:[~2018-02-21 23:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21 22:48 mmotm 2018-02-21-14-48 uploaded akpm
2018-02-21 22:48 ` akpm
2018-02-21 23:58 ` Randy Dunlap [this message]
2018-02-21 23:58   ` mmotm 2018-02-21-14-48 uploaded (mm/page_alloc.c on UML) Randy Dunlap
2018-02-22  7:20   ` Michal Hocko
2018-02-22  7:20     ` Michal Hocko
2018-02-22 10:38     ` Eugeniu Rosca
2018-02-22 10:38       ` Eugeniu Rosca
2018-02-22 10:38       ` Eugeniu Rosca
2018-02-22 12:59       ` Michal Hocko
2018-02-22 12:59         ` Michal Hocko
2018-02-22 13:08         ` Eugeniu Rosca
2018-02-22 13:08           ` Eugeniu Rosca
2018-02-22 13:08           ` Eugeniu Rosca
2018-02-22 13:26           ` Michal Hocko
2018-02-22 13:26             ` Michal Hocko
2018-02-25  0:50             ` Eugeniu Rosca
2018-02-25  0:50               ` Eugeniu Rosca
2018-02-25  0:50               ` Eugeniu Rosca

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=7bcc52db-57eb-45b0-7f20-c93a968599cd@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=erosca@de.adit-jv.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=mm-commits@vger.kernel.org \
    --cc=richard.weinberger@gmail.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 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.