Linux IIO development
 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/6 V2] staging:iio Build issue fixes
Date: Thu, 29 Jul 2010 10:38:23 -0700	[thread overview]
Message-ID: <4C51BC8F.30105@oracle.com> (raw)
In-Reply-To: <1280422251-13572-1-git-send-email-jic23@cam.ac.uk>

On 07/29/10 09:50, Jonathan Cameron wrote:
> Hi All,
> 
> This lot are in response to Randy Dunlap finding a number of build
> issues.  The final patch actually fixes a bug that has been there
> quite some time.
> 
> Sorry again for clearly not testing my previous series properly!
> 

Thanks for the quick update.
Acked-by: Randy Dunlap <randy.dunlap@oracle.com>


> 
> Jonathan Cameron (6):
>   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:adis16350 add dummy ring functions for no ring build case
>   staging:iio:ring_sw  Add select of triggers to avoid build issue.
>   staging:iio:ring_sw  remove unnecessary function stub.
>   staging:iio:ring_sw  Fix pointer arithmetic for 64bit arches by using
>     phys_addr_t
> 
>  drivers/staging/iio/Kconfig                |    1 +
>  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.c              |    2 +-
>  drivers/staging/iio/ring_sw.h              |    5 +++--
>  6 files changed, 22 insertions(+), 10 deletions(-)
> 


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

      parent reply	other threads:[~2010-07-29 17:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-29 16:50 [PATCH 0/6 V2] staging:iio Build issue fixes Jonathan Cameron
2010-07-29 16:50 ` [PATCH 1/6] staging:iio: iio_sw_ring_helper_state - add dummy case for no buffer builds Jonathan Cameron
2010-07-29 16:50 ` [PATCH 2/6] staging:iio:lis3l02dq add a thresh_timestamp field to state for no ring case Jonathan Cameron
2010-07-29 16:50 ` [PATCH 3/6] staging:iio:adis16350 add dummy ring functions for no ring build case Jonathan Cameron
2010-07-29 16:50 ` [PATCH 4/6] staging:iio:ring_sw Add select of triggers to avoid build issue Jonathan Cameron
2010-07-29 16:50 ` [PATCH 5/6] staging:iio:ring_sw remove unnecessary function stub Jonathan Cameron
2010-07-29 16:50 ` [PATCH 6/6] staging:iio:ring_sw Fix pointer arithmetic for 64bit arches by using phys_addr_t Jonathan Cameron
2010-07-29 17:38 ` Randy Dunlap [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=4C51BC8F.30105@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox