From: Alison Schofield <amsfield22@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: daniel.baluta@gmail.com, lars@metafoo.de
Subject: Re: [Outreachy kernel] IIO Coding Task Added
Date: Fri, 23 Sep 2016 09:53:44 -0700 [thread overview]
Message-ID: <20160923165343.GB6861@d830.WORKGROUP> (raw)
In-Reply-To: <CAEnQRZCkdXRBhjMfEQZYDenWxn4KdCwL+tmFwaMabEJZLerWDg@mail.gmail.com>
On Wed, Sep 21, 2016 at 11:01:57AM +0300, Daniel Baluta wrote:
> On Tue, Sep 20, 2016 at 10:43 PM, Alison Schofield <amsfield22@gmail.com> wrote:
> > An IIO Coding Task has been added to the IIO Task Page.
> > https://kernelnewbies.org/IIO_tasks
> >
> > So now you have 2 types of IIO Tasks:
> >
> > 1) Experimenting with the IIO Subsystem
> > Do these independently and submit to Daniel & Alison.
> >
> > 2) Coding Tasks
> > It's a single task but it applies to multiple drivers. You will
> > find your driver and claim it on the tasks page before working on
> > your patch. See the description for the details.
>
> I added one more IIO coding task suggested by Lars-Peter.
>
> It's about using sparse to detect endianness issues.
> Please read the documentation carefully and don't
> hesitate to ask questions :).
>
> Daniel.
I updated IIO Coding Task 2 just now with a bit of help to find
those IIO Endianess sparse warnings.
You can subscribe to the IIO Task page of kernelnewbies to be
notified of updates to the page automatically. Click 'subscribe'
link on page.
alisons
prev parent reply other threads:[~2016-09-23 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 19:43 IIO Coding Task Added Alison Schofield
2016-09-21 8:01 ` [Outreachy kernel] " Daniel Baluta
2016-09-23 16:53 ` Alison Schofield [this message]
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=20160923165343.GB6861@d830.WORKGROUP \
--to=amsfield22@gmail.com \
--cc=daniel.baluta@gmail.com \
--cc=lars@metafoo.de \
--cc=outreachy-kernel@googlegroups.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 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.