All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: Greg KH <greg@kroah.com>,
	akpm@linux-foundation.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH 0/3] staging:iio Build issue fixes
Date: Wed, 28 Jul 2010 13:10:32 -0700	[thread overview]
Message-ID: <4C508EB8.7020404@oracle.com> (raw)
In-Reply-To: <1280344057-18786-1-git-send-email-jic23@cam.ac.uk>

On 07/28/10 12:07, Jonathan Cameron wrote:
> Hi Greg,
> 
> Sorry about this lot.  I clearly missed one big case when build testing
> the last series of patches I sent you. Evidently never built them without
> buffering enabled.
> 
> Randy Dunlap found these 3 (posted to lkml in the thread,
> 
> mmotm 2010-07-27-14-56 uploaded (staging/iio)
> 
> I know of one remaining issue to do with some pointer arithmetic that won't
> work on 64 bit machines that I will try and get fixed shortly.

Thanks.  With these 3 patches applied, I still have this build warning:

In file included from linux-next-20100728/drivers/staging/iio/accel/lis3l02dq_core.c:31:
linux-next-20100728/drivers/staging/iio/accel/../ring_sw.h:223: warning: 'struct iio_ring_access_funcs' declared inside parameter list
linux-next-20100728/drivers/staging/iio/accel/../ring_sw.h:223: warning: its scope is only this definition or declaration, which is probably not what you want


> Jonathan Cameron (3):
>   staging:iio: iio_sw_ring_helper_state - add dummy case for no buffer
>     builds.
>   staging:iio:lis3l02dq add a thresh_timestamp field to state for no
>     ring case
>   staging:iio:adis1350 add dummy ring functions for no ring build case
> 
>  drivers/staging/iio/accel/lis3l02dq.h      |    2 ++
>  drivers/staging/iio/accel/lis3l02dq_core.c |   14 +++++++-------
>  drivers/staging/iio/imu/adis16350.h        |    8 ++++++++
>  drivers/staging/iio/ring_sw.h              |    3 +++
>  4 files changed, 20 insertions(+), 7 deletions(-)
> 


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2010-07-28 20:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27 21:56 mmotm 2010-07-27-14-56 uploaded akpm
2010-07-28  5:30 ` mmotm 2010-07-27 - WARNING in ec_parse_io_ports() Valdis.Kletnieks
2010-07-28 11:17   ` Thomas Renninger
2010-07-28  5:42 ` mmotm 2010-07-27 - nouveau lockdep issues Valdis.Kletnieks
2010-07-28  6:03   ` Marcin Slusarz
2010-07-28  6:03     ` Marcin Slusarz
2010-07-28 15:54 ` mmotm 2010-07-27-14-56 uploaded (staging/iio) Randy Dunlap
2010-07-28 18:32   ` Jonathan Cameron
2010-07-28 19:07     ` [PATCH 0/3] staging:iio Build issue fixes Jonathan Cameron
2010-07-28 20:10       ` Randy Dunlap [this message]
     [not found]         ` <4C509DBE.7000603@cam.ac.uk>
2010-07-29 15:52           ` Randy Dunlap
2010-07-28 19:07     ` [PATCH 1/3] staging:iio: iio_sw_ring_helper_state - add dummy case for no buffer builds Jonathan Cameron
2010-07-28 19:07     ` [PATCH 2/3] staging:iio:lis3l02dq add a thresh_timestamp field to state for no ring case Jonathan Cameron
2010-07-28 22:23 ` mmotm 2010-07-27 - hda-intel audio fails to initialize Valdis.Kletnieks
2010-07-28 22:23   ` Valdis.Kletnieks
2010-07-29  5:37   ` Takashi Iwai
2010-07-29 16:05     ` Valdis.Kletnieks
2010-07-29 16:05       ` Valdis.Kletnieks

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=4C508EB8.7020404@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=jic23@cam.ac.uk \
    --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.