On 14.01.2020 03:10, Michael Ellerman wrote: > Laurentiu Tudor <laurentiu.tu...@nxp.com> writes: >> Hello, >> >> On 13.01.2020 15:48, Timur Tabi wrote: >>> On 1/13/20 6:26 AM, Michael Ellerman wrote: >>>> I've never heard of it, and I have no idea how to test it. >>>> >>>> It's not used by qemu, I guess there is/was a Freescale hypervisor that >>>> used it. >>> >>> Yes, there is/was a Freescale hypervisor that I and a few others worked >>> on. I've added a couple people on CC that might be able to tell the >>> current disposition of it. >> >> More info on this: it's opensource and it's published here [1]. We still >> claim to maintain it but there wasn't much activity past years, as one >> might notice. >> >>>> But maybe it's time to remove it if it's not being maintained/used by >>>> anyone? >>> >>> I wouldn't be completely opposed to that if there really are no more >>> users. There really weren't any users even when I wrote the driver. >> >> There are a few users that I know of, but I can't tell if that's enough >> to justify keeping the driver. > > It is, I don't want to remove code that people are actually using, > unless it's causing unsustainable maintenance burden. > > But this should be easy enough to get fixed.
Right. I see that Stephen already came up with a proposal for a fix. > Could you or someone else at NXP volunteer to maintain this driver? That > shouldn't involve much work, other than fixing small things like this > warning. I can offer myself. I'll send a MAINTAINERS patch if nobody is against it. --- Best Regards, Laurentiu