So the plan is to only have sunxi-3.4 on one side and a "submitted
upstream" on the other side?
I'd welcome something intermediate, i.e. a branch that provides "the
most complete sunxi support in an uptodate kernel", and which is kept
uptodate (like sunxi-devel).
This could hold WiP for things that aren't ready for upstream submission
(and may languish in such a state for a long time, in case noone is
sufficiently motivated to refactor it for upstream).
> I wouldn't like sunxi-devel to become yet another vendor-BSP-like
> kernel.
I understand that. But at the same time, many important uses of
Allwinner SoCs currently require the sunxi-3.4 kernel and the
corresponding feature may never end up upstream, yet using a 3.4 kernel
in 2020 is likely to be a source of annoyances.
> But yeah, Boris MTD patches are elligible to sunxi-devel, they should
> definitely be in it.
How 'bout the consumer IR patches?
Stefan
--
You received this message because you are subscribed to the Google Groups
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
