All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] OMAP3 Fix compiler warning for v7_flush_dcache_all
Date: Sun, 19 Jul 2009 08:25:26 +0200	[thread overview]
Message-ID: <4A62BC56.1060800@googlemail.com> (raw)
In-Reply-To: <20090718203650.B265E832E416@gemini.denx.de>

Dear Wolfgang,

Wolfgang Denk wrote:
> Dear Tom Rix,
> 
> In message <1246392253-8431-2-git-send-email-Tom.Rix@windriver.com> you wrote:
>> On build of omap3 targets in MAKEALL, the *.ERR files have
>>
>> cpu.c: In function 'cleanup_before_linux':
>> cpu.c:64: warning: implicit declaration of function 'v7_flush_dcache_all'
>> cpu.c:64: warning: implicit declaration of function 'get_device_type
>>
>> The functions v7_flush_dcache_all and get_device_type are declared
>> in include/asm-arm/arch-omap3/sys_proto.h, so use this file to
>> declare the functions.
>>
>> Signed-off-by: Tom Rix <Tom.Rix@windriver.com>
>> ---
>>  cpu/arm_cortexa8/cpu.c |    3 +++
>>  1 files changed, 3 insertions(+), 0 deletions(-)
> 
> Applied, thanks.

Many thanks!

I'm not sure, Tom will have the details, but there might be a newer 
version of this patch?

http://lists.denx.de/pipermail/u-boot/2009-July/055543.html
http://lists.denx.de/pipermail/u-boot/2009-July/055544.html

Best regards

Dirk

  reply	other threads:[~2009-07-19  6:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 20:04 [U-Boot] Omap3 fix compiler warnings Tom Rix
2009-06-30 20:04 ` [U-Boot] [PATCH 1/1] OMAP3 Fix compiler warning for v7_flush_dcache_all Tom Rix
2009-07-02 21:00   ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-02 21:56     ` Tom
2009-07-03 21:00       ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-04 12:41         ` Tom
2009-07-04 14:44           ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-05  7:21           ` Dirk Behme
2009-07-18 20:36   ` Wolfgang Denk
2009-07-19  6:25     ` Dirk Behme [this message]
2009-07-19  8:55       ` Wolfgang Denk

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=4A62BC56.1060800@googlemail.com \
    --to=dirk.behme@googlemail.com \
    --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.