Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Pierre Ossman <pierre@ossman.eu>
To: Tony Lindgren <tony@atomide.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	linux-arm-kernel@lists.arm.linux.org.uk,
	linux-omap@vger.kernel.org,
	Adrian Hunter <adrian.hunter@nokia.com>
Subject: Re: [PATCH] mmc: Fix compile for omap_hsmmc.c (Re: New build error?)
Date: Wed, 8 Apr 2009 20:41:30 +0200	[thread overview]
Message-ID: <20090408204130.296ca789@mjolnir.ossman.eu> (raw)
In-Reply-To: <20090408001325.GG23823@atomide.com>

[-- Attachment #1: Type: text/plain, Size: 847 bytes --]

On Tue, 7 Apr 2009 17:13:27 -0700
Tony Lindgren <tony@atomide.com> wrote:

> * Russell King - ARM Linux <linux@arm.linux.org.uk> [090407 12:55]:
> > Caused by: 4a694dc915c9a223044ce21fc0d99e63facd1d64
> > 
> >     omap_hsmmc: Fix response type for busy after response
> > 
> > Error:
> > 
> > drivers/mmc/host/omap_hsmmc.c: In function 'mmc_omap_xfer_done':
> > drivers/mmc/host/omap_hsmmc.c:301: error: implicit declaration of function 'mmc_omap_fclk_lazy_disable'
> > 
> > Please submit a fix to Pierre for this, thanks.
> 
> Thanks for notifying about this. Pierre, here's a fix for this.
> 

Queued.

-- 
     -- Pierre Ossman

  WARNING: This correspondence is being monitored by the
  Swedish government. Make sure your server uses encryption
  for SMTP traffic and consider using PGP for end-to-end
  encryption.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2009-04-08 18:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07 19:55 New build error? Russell King - ARM Linux
2009-04-08  0:13 ` [PATCH] mmc: Fix compile for omap_hsmmc.c (Re: New build error?) Tony Lindgren
2009-04-08 18:41   ` Pierre Ossman [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=20090408204130.296ca789@mjolnir.ossman.eu \
    --to=pierre@ossman.eu \
    --cc=adrian.hunter@nokia.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=tony@atomide.com \
    /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