Rafał Miłecki 6c1852cb26 brcm47xx: image: use standard KERNEL_IMAGE to avoid warnings ... KERNEL_IMAGE is used as target rule so reusing the same name causes: Makefile:326: warning: overriding recipe for target `bin/brcm47xx/vmlinux.lzma' Makefile:326: warning: ignoring old recipe for target `bin/brcm47xx/vmlinux.lzma' Makefile:326: warning: overriding recipe for target `build_dir/target-mipsel_74kc+dsp2_uClibc-0.9.33.2/linux-brcm47xx_mips74k/vmlinux.lzma' Makefile:326: warning: ignoring old recipe for target `build_dir/target-mipsel_74kc+dsp2_uClibc-0.9.33.2/linux-brcm47xx_mips74k/vmlinux.lzma' Unfortunately this will cause copying vmlinux.lzma over and over like: cp vmlinux.lzma FOO-kernel.bin which is redundant on brcm47xx where we never modify kernel image. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 45178		2015-03-31 08:56:08 +00:00
..
base-files	brcm47xx: fix checking cross-vendors firmware images	2015-03-31 07:26:30 +00:00
generic	target/linux/*: more dead package cleanups	2014-07-10 20:05:43 +00:00
image	brcm47xx: image: use standard KERNEL_IMAGE to avoid warnings	2015-03-31 08:56:08 +00:00
legacy	target/linux/*: kmod-fs-ext{2,3} RIP	2014-07-10 19:16:15 +00:00
mips74k	brcm47xx: activate high mem for mips74k in the config	2014-08-07 20:22:00 +00:00
patches-3.14	kernel: backport queued bcm47xxpart changes	2015-01-27 22:08:14 +00:00
patches-3.18	brcm47xx: support SPROM/NVRAM prefixes	2015-03-17 07:07:17 +00:00
base-files.mk	add back the base-files/image code from brcm-2.4 to brcm47xx	2010-06-26 20:41:49 +00:00
config-3.14	kernel: remove GENERIC_NET_UTILS from platform configs	2015-03-06 07:55:57 +00:00
config-3.18	kernel: backport rest of bcma patches	2015-03-24 10:39:10 +00:00
Makefile	brcm47xx: switch to 3.18	2015-03-16 23:05:43 +00:00
modules.mk	brcm47xx: deactivate ssb and old phy code for new devices	2014-07-12 15:39:31 +00:00