On 2014-12-30 17:34, Andreas Färber wrote:
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
: 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?
In the script? I run an allmodconfig with the old config as a base. So all the new tristate options become =m and boolean options become =y. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org