<!-- Some styling for better description lists --><style type='text/css'>dt { font-weight: bold;float: left;display:inline;margin-right: 1em} dd { display:block; margin-left: 2em}</style>

   syoung: hi
   mchehab: hverkuil already said he won't be joining us today. Not sure about pinchartl and sailus
   syoung: <u>mchehab</u>: should https://www.spinics.net/lists/linux-media/msg151508.html go through the media tree? Not sure if it should be Acked or accepted.
   mchehab: if it were just dt stuff, acked-by would be the right way
   <br> but it contains change at sunxi-cir.c
   syoung: yes
   mchehab: what patch does it touch it?
   <br> drivers/media/rc/sunxi-cir.c
   <br> @@ -319,6 +319,7 @@ static int sunxi_ir_remove(struct platform_device *pdev)
   <br> static const struct of_device_id sunxi_ir_match[] = {
   <br> { .compatible = "allwinner,sun4i-a10-ir", },
   <br> { .compatible = "allwinner,sun5i-a13-ir", },
   <br> +	{ .compatible = "allwinner,sun6i-a31-ir", },
   <br> {},
   <br> patch 2 touches
   <br> if the changes are just like that, I'm perfectly fine on letting it be merged via DT tree
   syoung: it introduces some quirks here: https://patchwork.linuxtv.org/patch/56377/
   mchehab: I don't have any strong preference
   <br> I guess the point is: do you expect merging conflicts with such changes on your tree?
   syoung: the changes look fine to me and I don't expect merging conflicts
   <br> I don't have any preference
   mchehab: ok. IMO, merging via DT seems to be safer
   <br> as only two patches touch media; the rest touches generic stuff from DT
   syoung: So would that require your Acked-by: or should I ack it? I've looked at the patches and they look fine to me.
   mchehab: that may also be touched by other patches
   <br> the better is if you give your ack
   <br> I'll then give mine too
   syoung: ok. Thank you.
   mchehab: just replying to patch 00/12 should be enough
   <br> from my side, thanks to a hverkuil's collegue, we now have patches to port patchwork to a newer version...
   <br> applying them will be a challenge, though...
   -: mchehab hates how python manages versions
   mchehab: basically, I can't test the migration patches on Fedora
   <br> because the patchwork version we have doesn't work with Django 1.11