On Wed, 13 Apr 2016, Wolfgang Denk wrote:
> Dear Robert,
>
> In message you
> wrote:
> >
> > (in fact, i can see that of the several vendors that have
> > common/ directories, only ti/common/ has a Kconfig file, so i'm
> > concluding that a common/ directory containing a Kconfig file is
> > mo
Dear Robert,
In message you wrote:
>
> (in fact, i can see that of the several vendors that have common/
> directories, only ti/common/ has a Kconfig file, so i'm concluding
> that a common/ directory containing a Kconfig file is more the
> exception rather than the norm. ti/common/ seems like
currently refactoring a pile of (closely-related) board support code
and can clearly stuff a lot of duplicate code and header files into a
vendor-specific "common/" directory so just want to make sure i'm
doing this properly.
first, i can see from the top-level Makefile that a common board
di
3 matches
Mail list logo
