All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] ARMV7: Vexpress: Add missing MMC header
Date: Tue, 31 May 2011 22:26:43 +0200	[thread overview]
Message-ID: <4DE54F03.6060100@aribaud.net> (raw)
In-Reply-To: <4DE5364B.7050404@googlemail.com>

Hi Dirk,

Le 31/05/2011 20:41, Dirk Behme a ?crit :
> On 31.05.2011 20:18, Albert ARIBAUD wrote:
>> Le 23/05/2011 19:40, Dirk Behme a ?crit :
>>> From: Dirk Behme<dirk.behme@googlemail.com>
>>>
>>> Add a header file with the missing function prototype to fix
>>>
>>> ca9x4_ct_vxp.c: In function 'cpu_mmc_init':
>>> ca9x4_ct_vxp.c:93: warning: implicit declaration of function
>>> 'arm_pl180_mmci_init'
>>>
>>> introduced by commit "ARMV7: Vexpress: Add MMC support"
>>> (f0c64526b7e51ba997a0f1baf9e74e6d497b957e)
>>>
>>> Signed-off-by: Dirk Behme<dirk.behme@googlemail.com>
>>> CC: Andy Fleming<afleming@freescale.com>
>>> CC: Matt Waddel<matt.waddel@linaro.org>
>>>
>>> ---
>>>
>>> Changes in v2: Switch angle braces to quotes.
>>
>> Applied to u-boot-arm/next, thanks -- that will go in master at next
>> merge window.
>
> Thanks!
>
> Hmm, but why next? This would mean we release v2011.06 with the above
> warning? I thought that fixing warnings introduced while the merge
> window is one of the things a rc cycle is good for?

Hmm, you're right, I overlooked the date of the commit that caused the 
warning. Moving from next to master, then, with my apologies.

> Best regards
>
> Dirk

Amicalement,
-- 
Albert.

      reply	other threads:[~2011-05-31 20:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 17:40 [U-Boot] [PATCH v2] ARMV7: Vexpress: Add missing MMC header Dirk Behme
2011-05-31 18:18 ` Albert ARIBAUD
2011-05-31 18:41   ` Dirk Behme
2011-05-31 20:26     ` Albert ARIBAUD [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=4DE54F03.6060100@aribaud.net \
    --to=albert.u.boot@aribaud.net \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.