On 2016年03月23日 08:41, Dave Airlie wrote:
So although it's small framework or just subdirectory, we would need
someone who can manage the framework to avoid further confusion if
necessary.
So maybe it just doesn't need a maintainer, and maybe those the owner
of the bridge driver should be responsible for choosing the tree which
it's merged through along with updates. That's how dw-hdmi has been
managed on the whole.
It also means that the bridge driver maintainer is able to test changes
to the bridge driver, rather than having some over-arching bridge
subdirectory maintainer who doesn't have a clue whether the changes
work on the hardware.
IMHO, having bridge driver authors/maintainers look after their own
code has many advantages.
The author just send me a pull request with acks from a git tree
that hopefully both people agreed and tested from. No need to
send this via another maintainer layer.
Dave.
Sure, these patches looks cool, I think it's ready to be merged, I'd
like to give a Acked-by on rockchip side.
--
Ｍark Yao
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
