Re: [PATCH 3/4] kbuild: re-order the code to not parse unnecessary variables

2017-10-11 Thread Masahiro Yamada
2017-10-04 12:56 GMT+09:00 Masahiro Yamada : > The top Makefile is divided into some sections such as mixed targets, > config targets, build targets, etc. > > When we build mixed targets, Kbuild just invokes submake to process > them one by one. In this case, compiler-related variables like CC, >

Re: [PATCH 3/4] kbuild: re-order the code to not parse unnecessary variables

2017-10-09 Thread Masahiro Yamada
2017-10-10 7:03 GMT+09:00 Doug Anderson : > Hi, > > On Tue, Oct 3, 2017 at 8:56 PM, Masahiro Yamada > wrote: >> The top Makefile is divided into some sections such as mixed targets, >> config targets, build targets, etc. >> >> When we build mixed targets, Kbuild just invokes submake to process >>

Re: [PATCH 3/4] kbuild: re-order the code to not parse unnecessary variables

2017-10-09 Thread Doug Anderson
Hi, On Tue, Oct 3, 2017 at 8:56 PM, Masahiro Yamada wrote: > The top Makefile is divided into some sections such as mixed targets, > config targets, build targets, etc. > > When we build mixed targets, Kbuild just invokes submake to process > them one by one. In this case, compiler-related varia

[PATCH 3/4] kbuild: re-order the code to not parse unnecessary variables

2017-10-03 Thread Masahiro Yamada
The top Makefile is divided into some sections such as mixed targets, config targets, build targets, etc. When we build mixed targets, Kbuild just invokes submake to process them one by one. In this case, compiler-related variables like CC, KBUILD_CFLAGS, etc. are unneeded. Check what kind of ta