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 -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
