[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161020145204.77b37e6b@roar.ozlabs.ibm.com>
Date: Thu, 20 Oct 2016 14:52:04 +1100
From: Nicholas Piggin <npiggin@...il.com>
To: Michal Marek <mmarek@...e.com>
Cc: Adam Borowski <kilobyte@...band.pl>,
Mathieu OTHACEHE <m.othacehe@...il.com>,
Omar Sandoval <osandov@...ndov.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
adobriyan@...il.com, sfr@...b.auug.org.au, viro@...iv.linux.org.uk,
linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arch@...r.kernel.org
Subject: Re: [GIT PULL] kbuild changes for v4.9-rc1
On Wed, 19 Oct 2016 16:38:14 +0200
Michal Marek <mmarek@...e.com> wrote:
> Dne 18.10.2016 v 03:34 Nicholas Piggin napsal(a):
> > We should probably just bring all these arch patches through the
> > kbuild tree.
> >
> > I'm sorry for the breakage: I didn't realize it broke the build with
> > some configs, otherwise I would have given Michal a heads up before
> > his pull request, and worked to get this stuff in first.
>
> It breaks with some binutils versions only (and only with
> CONFIG_MODVERSIONS=y, of course).
Yeah this seems to be the issue, it apparently slipped past all the
automated builds. It seems like the existing CRC warnings in the tree
only trigger in rare circumstances too, so something could be a bit
fragile there.
Thanks,
Nick
Powered by blists - more mailing lists