All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Julian Veenstra <davidjulianveenstra@gmail.com>
To: linux-iio@vger.kernel.org, jic23@kernel.org
Subject: Re: GSoC IIO project: David Veenstra
Date: Thu, 8 Mar 2018 22:30:32 +0100	[thread overview]
Message-ID: <129b1789-3753-c6db-f854-d4b3e104f568@gmail.com> (raw)
In-Reply-To: <83BDCEE3-1946-40D9-94A9-B3B2EAA9E8C4@jic23.retrosnub.co.uk>

On 03/08/2018 12:45 PM, Jonathan Cameron 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=linux-iio&m=152050249930598&w=2
>> https://marc.info/?l=linux-iio&m=152050245530583&w=2
>>
>> Jonathan, in reply to
>> https://marc.info/?l=linux-iio&m=151784107521336&w=2, 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.
>
> Jonathan

Alright. I'd like to take a look at the ad2s1200 and the ad2s1210
driver, although I have
no concrete plan yet.

Best regards,
David Veenstra

  parent reply	other threads:[~2018-03-08 21:30 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
2018-03-08 21:30     ` David Julian Veenstra [this message]
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=129b1789-3753-c6db-f854-d4b3e104f568@gmail.com \
    --to=davidjulianveenstra@gmail.com \
    --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.