Re: [PATCH 2/3] drivers/hwtracing: make coresight-* explicitly non-modular

2015-10-13 Thread Mathieu Poirier
On 11 October 2015 at 19:35, Paul Gortmaker wrote: > None of the Kconfig currently controlling compilation of any of > the files here are tristate, meaning that none of it currently > is being built as a module by anyone. > > Lets remove the modular code that is essentially orphaned, so that >

Re: [PATCH 2/3] drivers/hwtracing: make coresight-* explicitly non-modular

2015-10-13 Thread Mathieu Poirier
On 11 October 2015 at 19:35, Paul Gortmaker wrote: > None of the Kconfig currently controlling compilation of any of > the files here are tristate, meaning that none of it currently > is being built as a module by anyone. > > Lets remove the modular code that is

[PATCH 2/3] drivers/hwtracing: make coresight-* explicitly non-modular

2015-10-11 Thread Paul Gortmaker
None of the Kconfig currently controlling compilation of any of the files here are tristate, meaning that none of it currently is being built as a module by anyone. Lets remove the modular code that is essentially orphaned, so that when reading the drivers there is no doubt they are builtin-only.

[PATCH 2/3] drivers/hwtracing: make coresight-* explicitly non-modular

2015-10-11 Thread Paul Gortmaker
None of the Kconfig currently controlling compilation of any of the files here are tristate, meaning that none of it currently is being built as a module by anyone. Lets remove the modular code that is essentially orphaned, so that when reading the drivers there is no doubt they are builtin-only.