[LEDE-DEV] [PATCH] brcm2708: rename all patches from raspberrypi git tree to use 999 prefix

Felix Fietkau nbd at nbd.name
Thu Mar 23 10:53:01 PDT 2017


On 2017-03-23 18:38, Rafał Miłecki wrote:
> On 2017-03-23 18:29, Felix Fietkau wrote:
>> On 2017-03-22 21:36, Rafał Miłecki wrote:
>>> From: Rafał Miłecki <rafal at milecki.pl>
>>> 
>>> 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'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
> 
> and have these patches applied on top of everything else.
> 
> Would something like 950 be a better choice?
I'm not sure using these critera will necessarily make things better
here, especially because it seems like we're mostly going to have
uncategorized and upstream/submitted patches.
950 would be okay, I just want to make sure that there's room for extra
patches *after* these ones.

- Felix




More information about the Lede-dev mailing list