All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hernán Gonzalez" <hernan@vanguardiasur.com.ar>
To: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>
Cc: David Julian Veenstra <davidjulianveenstra@gmail.com>,
	linux-iio@vger.kernel.org, jic23@kernel.org
Subject: Re: GSoC IIO project: David Veenstra
Date: Thu, 8 Mar 2018 11:00:20 -0300	[thread overview]
Message-ID: <CALfa3vGKDgxJp3qDmGzgViNi3hKOfvp3uwLu3w-2g0mjq9xDyw@mail.gmail.com> (raw)
In-Reply-To: <83BDCEE3-1946-40D9-94A9-B3B2EAA9E8C4@jic23.retrosnub.co.uk>

On Thu, Mar 8, 2018 at 8:45 AM, Jonathan Cameron
<jic23@jic23.retrosnub.co.uk> wrote:
>
>
> On 8 March 2018 10:58:23 GMT, David Julian Veenstra <davidjulianveenstra@=
gmail.com> wrote:
>>Dear IIO Community,
>>
>>For the Coding Task 01, I submitted the following patches:
>>https://marc.info/?l=3Dlinux-iio&m=3D152050249930598&w=3D2
>>https://marc.info/?l=3Dlinux-iio&m=3D152050245530583&w=3D2
>>
>>Jonathan, in reply to
>>https://marc.info/?l=3Dlinux-iio&m=3D151784107521336&w=3D2, do you have
>>a suggestion for a driver to move out of staging?
>
> In would take a look at the CDC or resolver drivers. I particular ABI on =
those..  let other list
>  know which you plan to take on to avoid duplication of effort.
>

Hi,

I'm also a student willing to apply to the GSoC, thus I'm chiming in.
I was thinking the same thing about avoiding the duplication of
effort.
I already started cleaning-up the cdc:ad7746 driver but didn't submit
the patches yet. If no one else is trying to move the same one out of
staging, I'd like to keep working on it.
So, if anyone has already started with that, please let me know so I
can focus on another one.

Cheers,

Hern=C3=A1n Gonzalez

  reply	other threads:[~2018-03-08 14:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-04 22:59 GSoC IIO project: David Veenstra David Julian Veenstra
2018-03-08 10:58 ` David Julian Veenstra
2018-03-08 11:45   ` Jonathan Cameron
2018-03-08 14:00     ` Hernán Gonzalez [this message]
2018-03-08 21:30     ` David Julian Veenstra
2018-03-08 23:17       ` Rodrigo Siqueira
2018-03-09 11:12         ` David Julian Veenstra

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=CALfa3vGKDgxJp3qDmGzgViNi3hKOfvp3uwLu3w-2g0mjq9xDyw@mail.gmail.com \
    --to=hernan@vanguardiasur.com.ar \
    --cc=davidjulianveenstra@gmail.com \
    --cc=jic23@jic23.retrosnub.co.uk \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.