From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Laura Abbott <lauraa@codeaurora.org>
Subject: Re: linux-next: Tree for Jan 27 (build failures due to 'don't offset memmap for flatmem')
Date: Tue, 27 Jan 2015 09:31:28 -0800 [thread overview]
Message-ID: <20150127173128.GA1555@roeck-us.net> (raw)
In-Reply-To: <20150127195123.46885d96@canb.auug.org.au>
On Tue, Jan 27, 2015 at 07:51:23PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150123:
>
> The arm64 tree gained a conflict against Linus' tree.
>
> The net-next tree gained conflicts against the arm-soc and net trees.
>
> The drm-panel tree gained a conflict against the drm tree.
>
> The wireless-drivers-next tree gained a build failure for which I reverted
> a commit.
>
> The block tree gained conflicts against the vfs and Linus' trees.
>
> The clockevents tree gained a conflict against the arm tree.
>
> The akpm tree lost a patch that turned up elsewhere.
>
> Non-merge commits (relative to Linus' tree): 5237
> 4877 files changed, 200964 insertions(+), 94565 deletions(-)
>
There are various build failures due to commit
'mm/page_alloc.c: don't offset memmap for flatmem',
which assumes that ARCH_PFN_OFFSET is defined for all architectures,
but it isn't. This is also the first use of ARCH_PFN_OFFSET outside
an architecture directory.
Build fails for mn10300, m68k_nommu, and avr32.
Guenter
next prev parent reply other threads:[~2015-01-27 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 8:51 linux-next: Tree for Jan 27 Stephen Rothwell
2015-01-27 17:31 ` Guenter Roeck [this message]
2015-02-02 18:31 ` linux-next: Tree for Jan 27 (build failures due to 'don't offset memmap for flatmem') Laura Abbott
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=20150127173128.GA1555@roeck-us.net \
--to=linux@roeck-us.net \
--cc=lauraa@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).