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: [PULL] IIO fixes for v3.7-rc1 set 2
Date: Fri, 2 Nov 2012 09:29:53 -0700 [thread overview]
Message-ID: <20121102162953.GB13600@kroah.com> (raw)
In-Reply-To: <5093A416.1080409@kernel.org>
On Fri, Nov 02, 2012 at 10:44:38AM +0000, Jonathan Cameron wrote:
> The following changes since commit 98f9c3c137cea016c57c9fd60b3caf88eb34e4cd:
>
> iio: Remove duplicates for light/ in Kconfig and Makefile (2012-10-19 19:44:06 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-3.7b
>
> for you to fetch changes up to 7243b785c43d9aedc7a584dab81bb3f26989d6a1:
>
> iio: hid-sensor: Use __devexit annotation for remove() (2012-11-02 09:57:57 +0000)
>
> ----------------------------------------------------------------
> Second round of fixes for IIO in 3.7 cycle, applies to 3.7-rc1.
>
> A mixed bag of fixes mainly for drivers but with one core
> double free fix.
>
> * A couple of little fixlets for the hid-sensors drivers.
> * Incorrect return value in adt7410
> * Fix up support for the adis16334 in the adis16400 driver.
> Turned out there were some bits and bobs that need to be
> handled different for this part. This seems like a large
> patch series but this is mostly because an additional chip
> specific callback is needed to handle the variations.
That is a big patch so late in the release cycle, is it really needed?
Is it a regression from 3.6? Or does it just fix a problem with a new
thing that showed up in 3.7-rc1? If the latter, how about we postpone
it and just mark the driver BROKEN or something?
thanks,
greg k-h
next prev parent reply other threads:[~2012-11-02 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 10:44 [PULL] IIO fixes for v3.7-rc1 set 2 Jonathan Cameron
2012-11-02 16:29 ` Greg KH [this message]
2012-11-02 21:17 ` 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=20121102162953.GB13600@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.