From: Greg KH <gregkh@linuxfoundation.org>
To: Josh Wu <josh.wu@atmel.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>
Subject: Re: [PULL] IIO fixes for 3.11 - set 4
Date: Sat, 21 Sep 2013 16:44:29 -0700 [thread overview]
Message-ID: <20130921234429.GA4272@kroah.com> (raw)
In-Reply-To: <52243CD8.7040308@atmel.com>
On Mon, Sep 02, 2013 at 03:23:04PM +0800, Josh Wu wrote:
> Hi, Jonathan and Greg
>
> On 9/1/2013 2:09 AM, Jonathan Cameron wrote:
> > On 08/29/13 22:32, Greg KH wrote:
> >> On Thu, Aug 29, 2013 at 10:22:33PM +0100, Jonathan Cameron wrote:
> >>> The following changes since commit d8dfad3876e4386666b759da3c833d62fb8b2267:
> >>>
> >>> Linux 3.11-rc7 (2013-08-25 17:43:22 -0700)
> >>>
> >>> are available in the git repository at:
> >>>
> >>> git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-3.11d
> >>>
> >>> for you to fetch changes up to 947b8ec78610fdfd891da249629f79cfa8e5da57:
> >>>
> >>> iio: at91: fix adc_clk overflow (2013-08-29 21:42:11 +0100)
> >>>
> >>> ----------------------------------------------------------------
> >>> 4th round of fixes for IIO in the 3.11 series.
> >>>
> >>> Another one patch pull request, this one for an overflow issue that
> >>> can occur in the at91 adc driver.
> >> How "necessary" is this for 3.11?
> >> Is it something that a user can hit today?
>
> The overflow only happened when user use a very high adc clock with a
> big start-up time.
> And our default start-up time in DTS is a low value (40ns). So I think
> it is rare case.
>
> >> Is it a regression from 3.10?
>
> No.
>
> >> Is it for a new driver?
>
> No.
>
> > No
> >> It's really late in the 3.11 cycle for me to want to send anything to
> >> Linus except for "this fixes a major issue" type patches. Can we just
> >> tag this for stable and have it show up in 3.11 after 3.12-rc1 is out?
> > Fine by me - have cc'd Josh and Maxime as they should be able to answer
> > the above better than me.
>
> So I am fine with this.
What ever happened with this, did I forget to pull them in, or Jonathan,
did you redo them in the last set of patches you sent to me?
thanks,
greg k-h
next prev parent reply other threads:[~2013-09-21 23:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 21:22 [PULL] IIO fixes for 3.11 - set 4 Jonathan Cameron
2013-08-29 21:32 ` Greg KH
2013-08-31 18:09 ` Jonathan Cameron
2013-09-02 7:23 ` Josh Wu
2013-09-21 23:44 ` Greg KH [this message]
2013-09-22 17:31 ` 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=20130921234429.GA4272@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=josh.wu@atmel.com \
--cc=linux-iio@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
/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.