On Wed, 2018-03-14 at 21:16 +0100, Arnd Bergmann wrote: > On Wed, Mar 14, 2018 at 9:03 PM, Doug Ledford <dledford@xxxxxxxxxx> wrote: > > On Tue, 2018-03-13 at 09:50 +0100, Arnd Bergmann wrote: > > > On Wed, Mar 7, 2018 at 11:12 AM, Arnd Bergmann <arnd@xxxxxxxx> wrote: > > > > On Wed, Mar 7, 2018 at 10:05 AM, Arnd Bergmann <arnd@xxxxxxxx> wrote: > > > > > > > > > A small complication is that I wrote the changelog for the build warning > > > > > on 32-bit architectures, which is more elaborate. kernelci.org for > > > > > some reasons currently skips the allmodconfig build on all 32-bit > > > > > architectures (I should ask the kernelci maintainers to change that), > > > > > > > > I see that Olof's build bot does have build results for arm32 > > > > allmodconfig, which is also big-endian, and reports the same > > > > errors that I described in the patch changelog. > > > > > > > > See > > > > > > > > http://arm-soc.lixom.net/buildlogs/arm-soc/v4.16-rc4-25-g41c42fe/ > > > > http://arm-soc.lixom.net/buildlogs/arm-soc/v4.16-rc4-25-g41c42fe/buildall.arm.allmodconfig.log.passed > > > > > > > > for today's results. > > > > > > > > This bot reports one other warning for arm32, but it's > > > > specific to the toolchain version used on that bot. > > > > I have a fix for that one as well, but there was some > > > > discussion on what the best approach would be. > > > > > > Any update on this? This is now the only remaining gcc warning we get on > > > allmodconfig builds for arm (both 32-bit and 64-bit) in linux-4.16-rc. > > > > > > > Do you need the full series to fix this (it looked that way to me)? > > I just double-checked, as I thought only the first one was needed, but > indeed we do need both. Hi Linus, Arnd sent in a two patch series and it got put into our for-next branch. But, the two patches are the *only* two remaining issues for the arm builds on the kernelci system. They would like to get this into for-rc so that the build failures stop. Are you OK with me just cherry-picking them from for-next to for-rc so I can send them to you? They'll show as duplicates in the next merge window, but should drop silently. -- Doug Ledford <dledford@xxxxxxxxxx> GPG KeyID: B826A3330E572FDD Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
Attachment:
signature.asc
Description: This is a digitally signed message part
