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