On Thu, Jan 27, 2011 at 09:28:14PM +, Chris Ball wrote:
> On Thu, Jan 27, 2011 at 03:33:32PM +, Chris Ball wrote:
> > Hi Russell,
> >
> > On Thu, Jan 27, 2011 at 12:19:01PM +, Russell King - ARM Linux wrote:
> > > FYI, I've now merged this into the ARM devel tree for the time being so
On Thu, Jan 27, 2011 at 03:33:32PM +, Chris Ball wrote:
> Hi Russell,
>
> On Thu, Jan 27, 2011 at 12:19:01PM +, Russell King - ARM Linux wrote:
> > FYI, I've now merged this into the ARM devel tree for the time being so
> > it doesn't get forgotten - which means it'll appear in linux-next
Hi Russell,
On Thu, Jan 27, 2011 at 12:19:01PM +, Russell King - ARM Linux wrote:
> FYI, I've now merged this into the ARM devel tree for the time being so
> it doesn't get forgotten - which means it'll appear in linux-next at some
> point if it isn't already there. (Mainly so I don't have to
On Tue, Jan 11, 2011 at 11:20:26PM +, Chris Ball wrote:
> Hi,
>
> On Tue, Jan 11, 2011 at 04:35:56PM +, Russell King - ARM Linux wrote:
> > Don't read the command response from the registers when either the
> > command timed out (because there was no response from the card) or
> > the chec
Hi,
On Tue, Jan 11, 2011 at 04:35:56PM +, Russell King - ARM Linux wrote:
> Don't read the command response from the registers when either the
> command timed out (because there was no response from the card) or
> the checksum on the response was invalid.
>
> Signed-off-by: Russell King
> --
Don't read the command response from the registers when either the
command timed out (because there was no response from the card) or
the checksum on the response was invalid.
Signed-off-by: Russell King
---
drivers/mmc/host/mmci.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(
