linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
To: Alexandru Ardelean <ardeleanalex@gmail.com>
Cc: dragos.bogdan@analog.com, "Hennerich,
	Michael" <michael.hennerich@analog.com>,
	stefan.popa@analog.com,
	Alexandru Ardelean <alexandru.Ardelean@analog.com>,
	linux-iio@vger.kernel.org, kernel-usp@googlegroups.com
Subject: Re: RFC on IIO AD7292 driver GSoC proposal
Date: Tue, 9 Apr 2019 09:16:55 -0300	[thread overview]
Message-ID: <20190409121655.qptymigvkitgo3iv@smtp.gmail.com> (raw)
In-Reply-To: <CA+U=DsokFDLC+kO61iErM12xp6ZBteYyfhrFKxexRzuumiFDqg@mail.gmail.com>

On 04/08, Alexandru Ardelean wrote:
> On Sat, Apr 6, 2019 at 10:46 PM Marcelo Schmitt
> <marcelo.schmitt1@gmail.com> 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?

> 
> > Thanks in advance,
> >
> > Marcelo

  reply	other threads:[~2019-04-09 12:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-06 19:45 RFC on IIO AD7292 driver GSoC proposal Marcelo Schmitt
2019-04-08  7:06 ` Alexandru Ardelean
2019-04-09 12:16   ` Marcelo Schmitt [this message]
2019-04-09 12:28     ` Alexandru Ardelean
2019-04-09 14:31     ` Daniel Baluta
2019-04-08  8:37 ` Crt Mori
2019-04-09 12:08   ` Marcelo Schmitt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190409121655.qptymigvkitgo3iv@smtp.gmail.com \
    --to=marcelo.schmitt1@gmail.com \
    --cc=alexandru.Ardelean@analog.com \
    --cc=ardeleanalex@gmail.com \
    --cc=dragos.bogdan@analog.com \
    --cc=kernel-usp@googlegroups.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=michael.hennerich@analog.com \
    --cc=stefan.popa@analog.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).