On Tue, Apr 9, 2019 at 3:17 PM Marcelo Schmitt <marcelo.schmitt1@xxxxxxxxx> wrote: > > On 04/08, Alexandru Ardelean wrote: > > On Sat, Apr 6, 2019 at 10:46 PM Marcelo Schmitt > > <marcelo.schmitt1@xxxxxxxxx> wrote: > > > > > > Hello. > > > > > > My name is Marcelo Schmitt, I'm a computer science student learning > > > how to contribute to the Linux Kernel in the IIO subsystem. I was told > > > by a friend that Google was encouraging people who contribute to open > > > source projects through the GSoC program and that there was a project > > > for developing a new IIO driver. I intend to continue contributing to > > > IIO and, if possible, engage in this GSoC project. As suggested by > > > GSoC organization, I shared a draft proposal for the project here > > > https://docs.google.com/document/d/1vOegyoC5b90jwLe1PBz4IbKGXaXMozi-RldS5OAZz4Y. > > > It would be really great if anyone could comment on it. > > > Sorry for sending it so close to dead line date. > > > > > > > Overall doc looks good. > > One note about the steps: ideally the AD7292 driver should not be put > > into staging, it's a new driver. > > Hence there is no reason to have a "move out-of-staging" step. > > > > The current IIO drivers in staging are there, because initially the > > IIO framework was done in staging, and some drivers were not updated > > because of time/priorities. > > Thanks Alexandru. > OK, understood. But where one should commit code for a driver in > development as will be the case for AD7292? iio main tree will > probably not be a good idea. Does any development branch exists? > testing2, compiletest? Hi Marcello, You wlll send the code for review to linux-iio list and when review done Jonathan will merge it in his linux-iio tree then it will send it upstream to Greg then Greg will send it to Linus. Your code should be placed inside drivers/iio directory. HTH, Daniel.
