On Tue, May 22, 2012 at 01:06:26PM +0300, Felipe Balbi wrote:
Hi,
On Tue, May 22, 2012 at 12:56:52PM +0300, Alexander Shishkin wrote:
quoted
quoted
Do you think it's a good idea to let user select binding driver directly
and the binding driver config depends on chipidea config?
I don't have a strong opinion on this, although I prefer it the way it
is now, because, imo:
* in case of =m (and that's the only sane way of compiling it anyway),
these all are compiled as modules, which you simply don't install if
you don't want them;
* all of them get compile-tested every time you change something in
the driver, which is a good thing;
only true for $(ARCH) builds. I would like to see these drivers being
compile tested on linux-next on all arches. Thus the patches I just
sent.
The idea is great. But
- how can I make sure it pass for all arch? There' 27 folder in arch/.
- it's hard to predict one driver depends on what.
- for embedded kernel, people like built-in drivers, and people will
have things they don't need at all.
Thanks
Richard
--
balbi