On Sun, Feb 4, 2018 at 5:23 PM, Jonathan Cameron <jic23@xxxxxxxxxx> wrote: > Hi All > > I was looking over what we have left in staging for any low hanging fruit > and came across the adis16201 driver. > > I was wondering if anyone would like to clean it up? > > This would make a good opportuntity for someone who is fairly new to > kernel development to make a useful contribution. > > To that end I've done a review as if it had been submitted as a new > driver. > > If you want to take this on, please reply to say so in order to avoid > several people looking at this one driver. Obviously if things change > and you then can't get to it reasonably quickly then 'hand it back' > on the mailing list. > > I'm happy to do this for a few more drivers if there are enough > interested people so do ping me if someone has claimed this one and you > would like a similar starting point. > > Ideally we would find someone who actually has hardware, but for the simple > stuff in this one I think we are unlikely to break anything that can't be > picked up in review. Hence I'm not totally bothered about it if no one > comes forward! > > Alison, Daniel. Feel free to add this to the outreachy task list if no > one else grabs it before the process starts again (just let us know if you are > doing that). Hi Jonathan, Will keep this in mind for next round of Outreachy that starts in March. I also submitted a proposal for GSoC: https://wiki.linuxfoundation.org/gsoc/2018-gsoc-iio-driver Let's see if this is accepted and we can have people working for the cleanups as a part of their application process. thanks, Daniel. -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
