[U-Boot] Should ARM custodian tree pull-reqs still go through the ARM tree ?

[Hans de Goede <hdegoede@redhat.com>]

Hi All,

Albert lately seems quite busy, and has a somewhat largish turn around time
for things like pull-reqs. This mail is in no way intended as a complaint
against Albert, we all have personal lives, and we all have periods were
we are more busy then other periods in our lives.

But now that we've Kconfig, and thus no longer have the big bad conflict
causing boards.cfg to deal with, I wonder if there is any added value in
all ARM pull-reqs going through Albert's u-boot-arm tree ?

I can understand that if some new ARM arch needs core changes that those
then need to go through Albert's tree and that any dependent changes then
need to be merged either after Albert's tree has been merged, or through
Albert's tree.

But for a lot of SoC specific work, e.g. stuff only touching files under
arch/arm/cpu/armv7/sunxi and under board/sunxi, I really see no benefit
in going through u-boot-arm, and I wonder if it would need be better
to instead send pull-reqs for merging directly into u-boot/master.

Regards,

Hans