linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: "Hennerich, Michael" <Michael.Hennerich@analog.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	driverdevel <devel@driverdev.osuosl.org>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"gregkh@suse.de" <gregkh@suse.de>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	Drivers <Drivers@analog.com>
Subject: Re: linux-next: Tree for October 13 (staging/iio)
Date: Thu, 14 Oct 2010 11:21:09 +0100	[thread overview]
Message-ID: <4CB6D995.9020907@cam.ac.uk> (raw)
In-Reply-To: <544AC56F16B56944AEC3BD4E3D59177130943738AE@LIMKCMBX1.ad.analog.com>

On 10/13/10 20:07, Hennerich, Michael wrote:
> Randy Dunlap wrote on 2010-10-13:
>> On Wed, 13 Oct 2010 15:45:22 +1100 Stephen Rothwell wrote:
>>
>>> Hi all,
>>>
>>> Changes since 20101012:
>>
>>
>> drivers/staging/iio/adc/ad7476.h:62: note: expected 'struct device *'
>> but argument is of type 'struct ad7476_state *'
>> drivers/staging/iio/adc/ad7476_core.c:48: error: too few arguments to
>> function 'ad7476_scan_from_ring'
> 
> Thanks!
> 
> That's due to an old prototype active when CONFIG_IIO_RING_BUFFER is not set.
> I'll fix that.
> 
>> drivers/staging/iio/adc/ad7476_core.c: At top level:
>> drivers/staging/iio/adc/ad7476_core.c:102: error:
>> 'IIO_SCAN_EL_TYPE_UNSIGNED' undeclared here (not in a function)
> 
> Jonathan,
> 
> Do we really need to guard the entire ring_generic.h header with
> 
> #ifdef CONFIG_IIO_RING_BUFFER
> ...
> 
> Some of these might be used, even when CONFIG_IIO_RING_BUFFER is not set.
> Or do we really need CONFIG_IIO_RING_BUFFER at all.
> Why not always provide it?
It's a fairly big chunk of code and I suspect a fair few of our users
(all the light sensors for starters) won't want it at all.  If anything
I'm keen to do a bit of reorganization of other bits of the core to
further cut down on the minimum present.

Move relevant functions out as needed or put stubs in place.  Perhaps we
can revisiting this question down the line, but I don't think we want to
make buffer support obligatory at the moment.

Jonathan
> 
>>
>> config is attached.
>>
>> ---
>> ~Randy
>> *** Remember to use Documentation/SubmitChecklist when testing your
>> code ***
> 
> Greetings,
> Michael
> 
> Analog Devices GmbH      Wilhelm-Wagenfeld-Str. 6      80807 Muenchen
> Sitz der Gesellschaft Muenchen, Registergericht Muenchen HRB 4036 Geschaeftsfuehrer Thomas Wessel, William A. Martin, Margaret Seif
> 
> 
> 

  reply	other threads:[~2010-10-14 10:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-13  4:45 linux-next: Tree for October 13 Stephen Rothwell
2010-10-13 16:38 ` linux-next: Tree for October 13 (net/3c59x) Randy Dunlap
2010-10-13 16:54   ` David Miller
2010-10-13 16:41 ` linux-next: Tree for October 13 (staging/iio) Randy Dunlap
2010-10-13 19:07   ` Hennerich, Michael
2010-10-14 10:21     ` Jonathan Cameron [this message]
2010-10-13 19:57 ` [PATCH -next] gpu/drm: fix build errors and kconfig dependency warnings Randy Dunlap
2010-10-14  0:38 ` linux-next: Tree for October 13 Andrew Morton
2010-10-14  0:41   ` H. Peter Anvin
2010-10-14  0:47     ` Andrew Morton
2010-10-14  2:55       ` Tony Breeds
2010-10-14  9:41       ` Feng Tang

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=4CB6D995.9020907@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=Drivers@analog.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=sfr@canb.auug.org.au \
    /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).