From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] sh: fix build error in cache.h
Date: Mon, 31 Oct 2011 11:35:15 +0900 [thread overview]
Message-ID: <4EAE0963.3000703@renesas.com> (raw)
In-Reply-To: <201110302225.35809.vapier@gentoo.org>
2011/10/31 11:25, Mike Frysinger wrote:
> On Sunday 30 October 2011 21:44:13 Yoshihiro Shimoda wrote:
>> In the latest U-Boot, the include/common.h includes the asm/cache.h.
>> So, the dcache_invalid_range() in the arch/sh/include/asm/cache.h is
>> multiple defination.
>
> i posted a fix for this already:
> http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/114290
>
> i don't think we want to go this route with inline markings since it bloats
> the code ...
Thank you for your point.
I should have looked at the mailing list more carefully before I submitted
my patch...
Thanks,
Yoshihiro Shimoda
prev parent reply other threads:[~2011-10-31 2:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 1:44 [U-Boot] [PATCH] sh: fix build error in cache.h Yoshihiro Shimoda
2011-10-31 2:25 ` Mike Frysinger
2011-10-31 2:35 ` Yoshihiro Shimoda [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=4EAE0963.3000703@renesas.com \
--to=yoshihiro.shimoda.uh@renesas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox