From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [GIT PULL v2] iio fixes for staging/staging-next.
Date: Tue, 17 Jul 2012 10:30:04 -0700 [thread overview]
Message-ID: <20120717173004.GA17718@kroah.com> (raw)
In-Reply-To: <50059E28.1080809@kernel.org>
On Tue, Jul 17, 2012 at 06:17:28PM +0100, Jonathan Cameron wrote:
>
> The following changes since commit 2b6e6b8042a9f783170b0a15e0550a075381726e:
>
> staging: comedi: rtd520: remove RtdDio0Read macro (2012-07-13 08:12:31 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-3.6b
>
> for you to fetch changes up to dcbc3c414e62faa4e1a1e17421f89eceea6bee30:
>
> iio staging: fix cast warning and cleanup alignment code (2012-07-15 17:33:18 +0100)
>
> ----------------------------------------------------------------
> IIO fixes for elements queued for 3.6 merge window.
>
> 3 types of fix here.
>
> 1) Incorrect pointer casting via phys_addr_t which causes
> trouble on some architectures.
> 2) request_irq and free_irq dev_id parameters not matching.
> 3) Inconsistencies in client_data for some i2c devices
> (writing one pointer and expecting another later).
Yeah!
That all looks great, thanks for working with me on these little
complaints, I appreciate it.
All pulled and pushed out, thanks.
greg k-h
next prev parent reply other threads:[~2012-07-17 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-15 18:19 [GIT PULL] iio fixes for staging/staging-next Jonathan Cameron
2012-07-17 0:58 ` Greg KH
[not found] ` <50059E28.1080809@kernel.org>
2012-07-17 17:30 ` Greg KH [this message]
2012-07-17 17:38 ` [GIT PULL v2] " Jonathan Cameron
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=20120717173004.GA17718@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--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.