Hi,
On Sat, Apr 21 2012, Russell King - ARM Linux wrote:
>> > Thanks, pushed to mmc-next for 3.4.
>>
>> (Actually, that's premature of me, sorry -- just noticed that this
>> is part of an RFC patchset. I'll wait for the rest of the patches.)
>
> It was previously posted as an entirely separate p
On Fri, Apr 20, 2012 at 10:35:59PM -0400, Chris Ball wrote:
> Hi,
>
> On Fri, Apr 20 2012, Chris Ball wrote:
> > On Fri, Apr 20 2012, Tony Lindgren wrote:
> >> * Russell King [120418 03:15]:
> >>> res can be one of several resources, as this variable is re-used several
> >>> times during probe.
Hi,
On Fri, Apr 20 2012, Chris Ball wrote:
> On Fri, Apr 20 2012, Tony Lindgren wrote:
>> * Russell King [120418 03:15]:
>>> res can be one of several resources, as this variable is re-used several
>>> times during probe. This can cause the wrong resource parameters to be
>>> passed to release_m
Hi,
On Fri, Apr 20 2012, Tony Lindgren wrote:
> * Russell King [120418 03:15]:
>> res can be one of several resources, as this variable is re-used several
>> times during probe. This can cause the wrong resource parameters to be
>> passed to release_mem_region().
>>
>> Get the original memory r
* Russell King [120418 03:15]:
> res can be one of several resources, as this variable is re-used several
> times during probe. This can cause the wrong resource parameters to be
> passed to release_mem_region().
>
> Get the original memory resource before calling release_mem_region().
>
> Sign
res can be one of several resources, as this variable is re-used several
times during probe. This can cause the wrong resource parameters to be
passed to release_mem_region().
Get the original memory resource before calling release_mem_region().
Signed-off-by: Russell King
---
drivers/mmc/host
