summaryrefslogtreecommitdiff
path: root/test
diff options
context:
space:
mode:
authorMasahiro Yamada <yamada.m@jp.panasonic.com>2014-07-22 10:57:19 +0900
committerTom Rini <trini@ti.com>2014-07-22 09:46:50 -0400
commitfbe79a17fddb7f0b11aa15b9c93e9a4a26165ed8 (patch)
treecae16c9e52baab221b079a468a4b86acf1228764 /test
parent61f06b143e92de70272627b4cd23d7b1e5af256e (diff)
downloadu-boot-imx-fbe79a17fddb7f0b11aa15b9c93e9a4a26165ed8.zip
u-boot-imx-fbe79a17fddb7f0b11aa15b9c93e9a4a26165ed8.tar.gz
u-boot-imx-fbe79a17fddb7f0b11aa15b9c93e9a4a26165ed8.tar.bz2
m68k: define __kernel_size_t as unsinged int again
Commit ddc94378d changed the definition of __kernel_size_t from unsigned int to unsigned long. It is true that it fixed warnings on some crosstools but it increased warnings on the others. The problem is that we cannot see consistency in terms of the typedef of __kernel_size_t on M68K architecture. However, I'd like to suggest to have __kernel_size_t to be unsigned int again. Rationale: [1] Linux Kernel defines __kernel_size_t on M68K as unsigned int. Let's stick to the Linux's way. [2] We want to build boards with popular pre-built toolchains, not the one locally-built by indivisuals. I think m68-linux-gcc which can be downloaded from www.kernel.org is the candidate for our _recommended_ toolchains. With this patch, all the m68k boards can be built without any warnings. Give it a try with the following crosstools: https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.6.3/ x86_64-gcc-4.6.3-nolibc_m68k-linux.tar.xz or https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.9.0/ x86_64-gcc-4.9.0-nolibc_m68k-linux.tar.xz (The latter is newer.) Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com> Cc: Simon Glass <sjg@chromium.org> Cc: Jason Jin <Jason.jin@freescale.com>
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions