All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Baluta <daniel.baluta@intel.com>
To: Alison Schofield <amsfield22@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: IIO Coding Task 2 ?
Date: Tue, 1 Mar 2016 11:43:20 +0200	[thread overview]
Message-ID: <56D56438.8000607@intel.com> (raw)
In-Reply-To: <20160301034750.GA2401@d830.WORKGROUP>



On 01.03.2016 05:47, Alison Schofield wrote:
> .........................snip...................
>> t > >We will make this in two steps:
>>>> * introduce API
>>>> * find a place where locking is not done
>>>> * use new API
>>>>
>>>> After IIO maintainer says this is OK:
>>>> * update all places with the new API.
>>>>
>>>> thanks,
>>>> Daniel.
>> Thanks for the directon.  I am working on that first step.
>> alisons
> Hi Daniel,
> I'm ready to send out the RFC PATCH, but I wasn't able to meet
> one of your requests.  I did not find a place where the locking
> was not done. The 'sample' is one where mlock was used with
> iio_buffer_enabled. I think it illustrates the API well because
> it clearly shows the before/after that would occur in other drivers.
> Send it?
> Thanks,
> alisons
>
Yes please :). Send the patches as RFC's, don't forget to Cc linux-iio 
mailing list.
Also, you can expand your searches to drivers/iio/.

thanks,
Daniel.



      reply	other threads:[~2016-03-01  9:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24 19:43 IIO Coding Task 2 ? Alison Schofield
     [not found] ` <56CEB5B4.5060605@intel.com>
2016-02-25  8:55   ` Daniel Baluta
2016-02-25 18:26     ` Alison Schofield
2016-03-01  3:47       ` Alison Schofield
2016-03-01  9:43         ` Daniel Baluta [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=56D56438.8000607@intel.com \
    --to=daniel.baluta@intel.com \
    --cc=amsfield22@gmail.com \
    --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.