On Sat, Oct 29, 2011 at 5:39 PM, Marek Vasut wrote:
>
> > From: Vikram Pandita
> >
> > omap_hsmmc.c: In function 'omap_hsmmc_protect_card':
> > omap_hsmmc.c:1273: error: 'pr_info' undeclared (first use in this function)
> > omap_hsmmc.c:1273: error: (Each undeclared identifier is reported only on
From: Lisa Carlson-Mcwhirter
Sent: Saturday, October 29, 2011 8:24 PM
To: Lisa Carlson-Mcwhirter
Subject: Your mailbox storage limit has been
Your mailbox storage limit has been
Your mailbox storage limit has been exceeded until you re-validate your
mailb
> From: Vikram Pandita
>
> omap_hsmmc.c: In function 'omap_hsmmc_protect_card':
> omap_hsmmc.c:1273: error: 'pr_info' undeclared (first use in this function)
> omap_hsmmc.c:1273: error: (Each undeclared identifier is reported only once
> omap_hsmmc.c:1273: error: for each function it appears in.)
From: Vikram Pandita
Data Buffer Error as per spec section 4.15.1.1.2
results when there is Underrun or Overrun condition.
This error is considered non-fatal and never gets reported.
Its a very good indication on things going wrong at system level,
like running memory at much slower speed.
This
From: Vikram Pandita
omap_hsmmc.c: In function 'omap_hsmmc_protect_card':
omap_hsmmc.c:1273: error: 'pr_info' undeclared (first use in this function)
omap_hsmmc.c:1273: error: (Each undeclared identifier is reported only once
omap_hsmmc.c:1273: error: for each function it appears in.)
omap_hsmmc.
In commit a3c76eb9 (mmc: replace printk with appropriate
display macro) the opening parenthesis of pr_info was missing.
Signed-off-by: Juergen Kilb
---
drivers/mmc/host/omap_hsmmc.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/
Hi,
On Sat, Oct 29 2011, Juergen Kilb wrote:
> In commit a3c76eb9 (mmc: replace printk with appropriate
> display macro) the opening parenthesis of pr_info was missing.
>
> Signed-off-by: Juergen Kilb
> ---
> drivers/mmc/host/omap_hsmmc.c |2 +-
> 1 files changed, 1 insertions(+), 1 deletion
On Sat, Oct 29, 2011 at 12:47:57AM +0200, Sascha Hauer wrote:
> My main concern with the fixed regulator is that it needs quite much
> boilerplate code just to say that we have no regulator at all for a
> given device. That could also be handled with a helper function which
> registers a fixed reg
On Fri, 28 Oct 2011, Vikram Pandita wrote:
> From: Vikram Pandita
>
> Data Buffer Error as per spec section 4.15.1.1.2
> results when there is Underrun or Overrun condition.
>
> This error is considered non-fatal and never gets reported.
> Its a very good indication on things going wrong at sys
