On 27.09.18 23:08:09, Leonardo Brás wrote: > This Patchset changes some driver's Makefile to allow them building > using the command 'make drivers/DRIVERNAME', if compatible. > > The changed drivers would return error if the above command was run > on them, after an x86 allyesconfig. I don't see what you are trying to achieve here. Why shouldn't the command fail if it is not the intended way to call it? There are a couple of use cases where drivers/ is used to share common code over different archs and it is not always the intention to build them in drivers/ directly. > > The main reason of this patchset is to allow building lists of > drivers looking for warnings and errors to be fixed. If a list is the intention here, aren't there other ways to create it other than using drivers/*? -Robert > > I see this change as a new feature, not a bugfix. I understand > the default bahavior may be building with a simple 'make', but I > believe adding this new possibility will not be harmful. > > My main objective is to allow developers with low processing power > to do changes in the kernel and look bugs using free services like > GiltabCI, before submitting to community. > > If there is any interest helping/using this, I have a prototype in: > https://gitlab.com/LeoBras/linux-next
