On 23 March 2017 at 18:57, Álvaro Fernández Rojas <[email protected]> wrote: > El 23/03/2017 a las 18:38, Rafał Miłecki escribió: >> On 2017-03-23 18:29, Felix Fietkau wrote: >>> On 2017-03-22 21:36, Rafał Miłecki wrote: >>>> From: Rafał Miłecki <[email protected]> >>>> >>>> Right now all brcm2708 patches are extracted from the non-mainline >>>> raspberrypi/linux git tree. Many of them are hacks and/or are unneeded >>>> in LEDE. Raspberry Pi is getting better and better mainline support so >>>> it would be nice to finally start maintaining patches in a cleaner way: >>>> 1) Backport patches accepted in upstream tree >>>> 2) Start using upstream drivers >>>> 3) Pick only these patches that are needed for more complete support >>>> >>>> Handling above tasks requires grouping patches - ideally using the same >>>> prefixes as generic ones. It means we should rename existing patches to >>>> use some high prefix. This will allow e.g. use 0xx for backported code. >>> I agree with the split, but could you please use a number much lower >>> than 999? ;) > I also agree with the split, but I have to warn you that I may not be able to > achieve this right now since I haven't got much free time lately... > >> >> I'd like to have "access" to all standard prefixes: >> >> 0xx - upstream backports >> 1xx - code awaiting upstream merge >> 2xx - kernel build / config / header patches >> 3xx - architecture specific patches >> 4xx - mtd related patches (subsystem and drivers) >> 5xx - filesystem related patches >> 6xx - generic network patches >> 7xx - network / phy driver patches >> 8xx - other drivers >> 9xx - uncategorized other patches > I think those patches fit into the "uncategorized other patches" category so > why don't we use 900-?
I'd also like to have space for "uncategorized other patches" added before patches backported from raspberrypi/linux. 950 would allow using 900-949 numbers for such stuff. And in case we need patches on top of raspberrypi/linux (as Felix suggested) we may use 951-999. -- Rafał _______________________________________________ Lede-dev mailing list [email protected] http://lists.infradead.org/mailman/listinfo/lede-dev
