Am 30.12.2014 um 17:01 schrieb Michal Marek:
On 2014-12-29 09:38, Matwey V. Kornilov wrote:
2014-12-28 20:53 GMT+03:00 Andreas Färber <afaerber@suse.de>:
Who is going to maintain these files after they get applied? I don't have time for daily kernel config updates...
I thought Michal had the script, allowing doing daily updates automatic.
Well, I'm semi-automatically maintaining the 'vanilla' and 'linux-next' branches that track mainline and linux-next, respectively. These branches merge any changes in the vanilla configs in the 'master' branch. However, in the master branch, the new configs need to be maintained by somebody knowledgeable about ARM.
How do you handle new options? Do they all become =m and someone needs to change them to =y where needed?
Also, might this impact publishing of existing flavors in Kernel:HEAD?
Don't understand how
Yeah, this is not a problem.
Did you actually try building this new flavor along the previous ones? In the past we had issues with armv7l default and lpae flavors not finishing to build in time for the next daily Kernel:HEAD update. If not all flavors in a repo finish building, none of them gets published. In Matwey's patch it looked as if only the vanilla config was active. For Kernel:linux-next that should not be an issue, as only the vanilla flavor would be active iiuc, but for Kernel:HEAD it seems like a risk. Cheers, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton; HRB 21284 (AG Nürnberg)