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,
Jonathan Zhang <zjzhang@codeaurora.org>,
Andrew Morton <akpm@linux-foundation.org>,
Matt Fleming <matt.fleming@intel.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: linux-next: Tree for Sep 18 (build failures, up to 10/02)
Date: Fri, 2 Oct 2015 09:16:37 -0700 [thread overview]
Message-ID: <20151002161637.GA17786@roeck-us.net> (raw)
In-Reply-To: <20150918142204.GA17018@roeck-us.net>
On Fri, Sep 18, 2015 at 07:22:04AM -0700, Guenter Roeck wrote:
> On Fri, Sep 18, 2015 at 02:08:10PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20150917:
> >
> > I used the h8300 tree from next-20150828 since the current tree has been
> > rebased onto something very old :-(
> >
> > The bluetooth tree still had its build failure.
> >
> > The tip tree gained a conflict against Linus' tree.
> >
> > The akpm-current tree lost its build failure.
> >
> > Non-merge commits (relative to Linus' tree): 1938
> > 1581 files changed, 83940 insertions(+), 23948 deletions(-)
> >
>
> Build failures:
>
> ia64:defconfig
> ia64:allnoconfig
>
> drivers/built-in.o: In function `efi_mem_attributes':
> (.text+0xde962): undefined reference to `memmap'
> drivers/built-in.o: In function `efi_mem_attributes':
> (.text+0xde971): undefined reference to `memmap'
>
> Bisect points to 'efi, x86: Rearrange efi_mem_attributes()'.
> On a side note, 'memmap' is really a bad name for a global variable,
> As the patch description suggests, the variable does not exist for ia64,
> so the build failure is not entirely unexpected.
>
The build for ia64 still fails in next-20151002. Maybe it is time
to revert the offending commit ? After all, the commit was supposed
to _fix_ a problem associated with ia64, not to make it completely
non-buildable.
Guenter
next prev parent reply other threads:[~2015-10-02 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 4:08 linux-next: Tree for Sep 18 Stephen Rothwell
2015-09-18 14:22 ` linux-next: Tree for Sep 18 (build failures) Guenter Roeck
2015-10-02 16:16 ` Guenter Roeck [this message]
2015-10-03 22:26 ` linux-next: Tree for Sep 18 (build failures, up to 10/02) Matt Fleming
2015-10-10 16:26 ` Matt Fleming
2015-10-11 9:06 ` [tip:core/efi] efi: Use the generic efi.memmap instead of 'memmap ' tip-bot for Matt Fleming
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=20151002161637.GA17786@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=zjzhang@codeaurora.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).