On Tue, 2017-01-03 at 22:19 +0100, Arnd Bergmann wrote: > Sounds good to me. My original series contained four more patches that > I did not post again after there was some concern[1] that we did not > come to a conclusion on: > > isdn: gigaset: remove i4l code Let me repeat that I'm fine with a patch that does that. > isdn: move isdnhdlc out of i4l > isdn: i4l: move hisax driver to staging > isdn: move i4l to staging > > I can post those as well, at least I think the first two are helpful > for untangling i4l from the rest of ISDN. I also still think that > moving hisax and i4l to staging is reasonable given the state of > that code, even if there are a couple of users today. There are? And even if there are: is there any reason to expect that moving the rest of i4l to staging will result in anything other than a stream of checkpatch cleanups? How often did a bunch of drivers re-enter the tree after being sent to staging? Paul Bolle -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html