All of lore.kernel.org
 help / color / mirror / Atom feed
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] iio fixes for staging/staging-next.
Date: Mon, 16 Jul 2012 17:58:43 -0700	[thread overview]
Message-ID: <20120717005843.GA16382@kroah.com> (raw)
In-Reply-To: <500309B8.60009@kernel.org>

On Sun, Jul 15, 2012 at 07:19:36PM +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 fixes-togreg
> 
> for you to fetch changes up to dcbc3c414e62faa4e1a1e17421f89eceea6bee30:
> 
>   iio staging: fix cast warning and cleanup alignment code (2012-07-15 17:33:18 +0100)
> 
> ----------------------------------------------------------------
> 3 types of fix here.

Subsystem?  Some kind of hint please?

> 
> 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).

Also, none of this showed up in the tag listed above.  And odds are, the
above is really a branch, not a tag, did you forget to push the tag and
wait for it to propage to the public side before creating this pull
request?

Care to try it again?

Oh, at least you aren't line-wrapping :)

thanks,

greg k-h

  reply	other threads:[~2012-07-17  0:58 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 [this message]
     [not found]   ` <50059E28.1080809@kernel.org>
2012-07-17 17:30     ` [GIT PULL v2] " Greg KH
2012-07-17 17:38       ` 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=20120717005843.GA16382@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.