From: Jonathan Cameron <jic23@kernel.org>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Jonathan Cameron <jic23@jic23.retrosnub.co.uk>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH 1/2] adc: exynos_adc: Convert to devm_ioremap_resource()
Date: Wed, 22 May 2013 22:19:40 +0100 [thread overview]
Message-ID: <519D366C.6050209@kernel.org> (raw)
In-Reply-To: <CAK9yfHxwk77Otgu1FOu5eUAMpvNN8pVtK7UvxJ0BKLD3i2A_Gw@mail.gmail.com>
On 04/30/2013 03:59 AM, Sachin Kamat wrote:
> On 29 April 2013 23:57, Lars-Peter Clausen <lars@metafoo.de> wrote:
>> On 04/29/2013 07:18 PM, Sachin Kamat wrote:
>>> Hi Jonathan,
>>>
>>> On 15 April 2013 16:16, Jonathan Cameron <jic23@jic23.retrosnub.co.uk> wrote:
>>>> On 15/04/13 09:22, Sachin Kamat wrote:
>>>>>
>>>>> On 3 April 2013 11:53, Sachin Kamat <sachin.kamat@linaro.org> wrote:
>>>>>>
>>>>>> Use the newly introduced devm_ioremap_resource() instead of
>>>>>> devm_request_and_ioremap() which provides more consistent error handling.
>>>>>>
>>>>>> Signed-off-by: Sachin Kamat <sachin.kamat@linaro.org>
>>>>
>>>> Not sure why I missed this one. I think I marked the entire thread
>>>> as not ready based on the responses to patch 2. Clearly nothing wrong
>>>> with this one! Will pick up for the next cycle now as I think it
>>>> is a cleanup rather than an actual bug fix?
>>>>
>>>> Thanks for the ping.
>>>
>>> Looks like this patch has still not made it to your tree as I did not
>>> find it in Greg's pull request to Linus.
>>> I however saw two of my other iio patches in his pull request.
>>
>> The IIO tree was already closed at that point, so "next cycle" refers to 3.11
>> in this case.
>
> Oh OK. Got it :)
> Thanks for the clarification.
>
Now finally applied to the togreg branch of iio.git.
Will hopefully send upstream sometime over next few days at which point it will hit
linux-next and be ready for the next merge cycle.
Jonathan
prev parent reply other threads:[~2013-05-22 21:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 6:23 [PATCH 1/2] adc: exynos_adc: Convert to devm_ioremap_resource() Sachin Kamat
2013-04-03 6:23 ` [PATCH 2/2] adc: exynos_adc: Fix incorrect variable type Sachin Kamat
2013-04-03 17:27 ` Naveen Krishna Ch
2013-04-04 3:35 ` Sachin Kamat
2013-04-15 8:22 ` [PATCH 1/2] adc: exynos_adc: Convert to devm_ioremap_resource() Sachin Kamat
2013-04-15 10:46 ` Jonathan Cameron
2013-04-15 11:07 ` Sachin Kamat
2013-04-29 17:18 ` Sachin Kamat
2013-04-29 18:27 ` Lars-Peter Clausen
2013-04-30 2:59 ` Sachin Kamat
2013-05-22 21:19 ` Jonathan Cameron [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=519D366C.6050209@kernel.org \
--to=jic23@kernel.org \
--cc=jic23@jic23.retrosnub.co.uk \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=sachin.kamat@linaro.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