On 24 April 2014 14:27, Russell King - ARM Linux wrote:
> On Thu, Apr 24, 2014 at 01:32:02PM +0200, Ulf Hansson wrote:
>> On 24 April 2014 13:18, Russell King - ARM Linux
>> wrote:
>> > That may be the case, but that would be an additional modification, and so
>> > should be a separate patch.
>>
On Thu, Apr 24, 2014 at 01:32:02PM +0200, Ulf Hansson wrote:
> On 24 April 2014 13:18, Russell King - ARM Linux
> wrote:
> > That may be the case, but that would be an additional modification, and so
> > should be a separate patch.
>
> I just thought it make sense to include it here - it's reall
On 24 April 2014 13:18, Russell King - ARM Linux wrote:
> On Thu, Apr 24, 2014 at 09:32:30AM +0200, Ulf Hansson wrote:
>> On 23 April 2014 21:08, Russell King wrote:
>> > We don't need these hooks in order to insert code in these paths, we
>> > can just provide our own handlers and call the main
On Thu, Apr 24, 2014 at 09:32:30AM +0200, Ulf Hansson wrote:
> On 23 April 2014 21:08, Russell King wrote:
> > We don't need these hooks in order to insert code in these paths, we
> > can just provide our own handlers and call the main sdhci handlers as
> > appropriate.
> >
> > Signed-off-by: Russ
On 23 April 2014 21:08, Russell King wrote:
> We don't need these hooks in order to insert code in these paths, we
> can just provide our own handlers and call the main sdhci handlers as
> appropriate.
>
> Signed-off-by: Russell King
> ---
> drivers/mmc/host/sdhci-of-esdhc.c | 55
>
We don't need these hooks in order to insert code in these paths, we
can just provide our own handlers and call the main sdhci handlers as
appropriate.
Signed-off-by: Russell King
---
drivers/mmc/host/sdhci-of-esdhc.c | 55 +--
1 file changed, 36 insertions(+)
