On 07/22/2015 12:06 AM, Uwe Kleine-König wrote:
While I stumbled over the calls to gpiod_get variants in the etraxfs serial driver I noticed several problems with that driver. I pointed them out inhttp://www.spinics.net/lists/linux-serial/msg17794.html . If you read the follow-ups Jesper Nilsson then said: I can push a patch that just drops all signal handling (since it's bogus ATM), or you can ignore the driver as currently implemented.
If you want to mark the driver as BROKEN due to those other problems, go ahead, and I'll drop the architecture from my tests. But it should not be marked BROKEN because you did not update an API.
I explicitly did the latter. Apart from that single driver I fixed all users. @Jesper: You said you poked Niklas to care for that. Any news from that front? I'm all for the usual habit that API changes should be handled by the API changer. But if the code was already relying on undefined behaviour before the change and fixing that needs testing on the respective hardware, I think pushing the needed work back to the driver owner is fine. IMHO a simple build fix that doesn't fix the brokeness isn't that helpful here.
The driver works fine for me (in qemu), possibly because qemu doesn't use/need modem lines. Guenter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
