linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Jonathan Cameron <jic23@cam.ac.uk>,
	Michael Hennerich <michael.hennerich@analog.com>,
	linux-iio@vger.kernel.org,
	device-drivers-devel@blackfin.uclinux.org, drivers@analog.com
Subject: Re: [PATCH 1/4] staging:iio: Factor out event handling into its own file
Date: Sun, 18 Dec 2011 20:46:29 +0100	[thread overview]
Message-ID: <4EEE4315.1080200@metafoo.de> (raw)
In-Reply-To: <4EEE2FC3.5000705@kernel.org>

On 12/18/2011 07:24 PM, Jonathan Cameron wrote:
> On 12/18/2011 06:19 PM, Jonathan Cameron wrote:
>> On 12/16/2011 05:12 PM, Lars-Peter Clausen wrote:
>>> The core iio file has gotten quite cluttered over time. This patch moves
>>> the event handling code into its own file.
>> A small comment here wrt to ease of review. When doing
>> a whole scale move like this, it is helpful to state
>> where any necessary code changes were... That way I can
>> just assume you cut and paste the rest rather than having
>> to check that.
>>>
>>> This has also the advantage that industrialio-core.c is now closer again to
>>> its counterpart in the outofstaging branch.
>> Definitely in favour of this change.
>>
>> Assuming it isn't in a later patch, there are a few undocumented
>> structure elements that could do with documenting ;)
>> More 'interestingly' there are a few that don't exist and are
>> documented.  All my fault of course, but seeing as you are
>> cleaning this code up... (looks hopeful)
>> Obviously shouldn't be part of this patch.  Either insert
>> one fixing it first, or do it at the end as a cleanup patch.
>>
>> So all in all, the patch is fine, I just noticed some unrelated bits
>> whilst reading it ;)  Events as you have no doubt noticed are
>> probably our most dubious corner (or were until this set).
>>>
> I really ought not to leave my build tests running in the background
> whilst sending emails acking things.  Looks like you have some issues...
> 
> drivers/staging/iio/industrialio-event.c:84:17: error: undefined
> identifier 'TASK_INTERRUPTIBLE'
> drivers/staging/iio/industrialio-event.c:114:23: error: undefined
> identifier 'TASK_INTERRUPTIBLE'
> drivers/staging/iio/industrialio-event.c:114:23: error: undefined
> identifier 'signal_pending'
> drivers/staging/iio/industrialio-event.c:114:23: error: undefined
> identifier 'schedule'
> 
> Can't chase this down right now, but I'm guessing missing header
> at least on arm.
> 
> adding include of sched.h does the job.

Makes me wonder if wait.h should include sched.h. But I'll add it the this
patch as well.

      reply	other threads:[~2011-12-18 19:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16 17:12 [PATCH 1/4] staging:iio: Factor out event handling into its own file Lars-Peter Clausen
2011-12-16 17:12 ` [PATCH 2/4] staging:iio:events: Use kfifo for event queue Lars-Peter Clausen
2011-12-18 21:42   ` Jonathan Cameron
2011-12-18 21:43     ` Jonathan Cameron
2011-12-16 17:12 ` [PATCH 3/4] staging:iio:events: Use waitqueue lock to protect " Lars-Peter Clausen
2011-12-18 21:54   ` Jonathan Cameron
2011-12-19  8:25     ` Lars-Peter Clausen
2011-12-19  8:31       ` J.I. Cameron
2011-12-19  8:54         ` J.I. Cameron
2011-12-16 17:12 ` [PATCH 4/4] staging:iio:events: Add poll support Lars-Peter Clausen
2011-12-19  8:46   ` jic23
2011-12-18 18:19 ` [PATCH 1/4] staging:iio: Factor out event handling into its own file Jonathan Cameron
2011-12-18 18:24   ` Jonathan Cameron
2011-12-18 19:46     ` Lars-Peter Clausen [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=4EEE4315.1080200@metafoo.de \
    --to=lars@metafoo.de \
    --cc=device-drivers-devel@blackfin.uclinux.org \
    --cc=drivers@analog.com \
    --cc=jic23@cam.ac.uk \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=michael.hennerich@analog.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).