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 11:58:23 +0100 [thread overview]
Message-ID: <516a7508-c151-52ec-d7dc-dc2df8dba1e3@gmail.com> (raw)
In-Reply-To: <9a4d5126-2087-bb75-88ed-f4a902ff7603@gmail.com>
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?
Best regards,
David Veenstra
On 03/04/2018 11:59 PM, David Julian Veenstra wrote:
> Dear IIO Comunity,
>
> Hello, I'm David Veenstra. Currently, I'm a master of Logic
> (theoretical computer science) student at the University of Amsterdam.
> Before that I completed a bachelor in Computer Science, also at the UvA.
>
> My first experience with drivers was during the development of my
> bachelor thesis. Among others things, I investigated what API was
> available for writing virtualized drivers for KVM and Xen. Since, then
> I have been working on a hobby OS, and also on virtio PCIe drivers.
> Furthermore, during a summer internship, I have written a prototype
> linux nic driver for an FPGA. I have greatly enjoyed this experiences,
> and hence would very much like to join this GSoC project.
>
> It is my understanding that the solutions for the tasks should be sent
> in private, so I will send it to the mentor: Daniel Baluta.
>
> Best regards,
> David Veenstra
next prev parent reply other threads:[~2018-03-08 10:58 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 [this message]
2018-03-08 11:45 ` Jonathan Cameron
2018-03-08 14:00 ` Hernán Gonzalez
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=516a7508-c151-52ec-d7dc-dc2df8dba1e3@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.