From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, 1/3] i2c: eliminate warnings in i2c_reloc_fixup function
Date: Thu, 17 Oct 2013 08:27:48 +0200 [thread overview]
Message-ID: <525F8364.70506@denx.de> (raw)
In-Reply-To: <1381899184-23315-2-git-send-email-yamada.m@jp.panasonic.com>
Hello Masahiro,
Am 16.10.2013 06:53, schrieb Masahiro Yamada:
> The prototype of handlers had changed.
> This commit uses cast with (void *) rather than
> the handler-specific prototype.
>
> Signed-off-by: Masahiro Yamada<yamada.m@jp.panasonic.com>
>
> ---
> Note:
> The body of i2c_reloc_fixup function is surrounded by
> #if defined(CONFIG_NEEDS_MANUAL_RELOC) ... #endif
>
> avr32, m68k, nds32, sparc defines this macro.
>
>
> drivers/i2c/i2c_core.c | 12 +++++-------
> 1 file changed, 5 insertions(+), 7 deletions(-)
Applied to u-boot-i2c.git
Thanks!
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2013-10-17 6:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 4:53 [U-Boot] [PATCH 0/3] All M68K boards are broken Masahiro Yamada
2013-10-16 4:53 ` [U-Boot] [PATCH 1/3] i2c: eliminate warnings in i2c_reloc_fixup function Masahiro Yamada
2013-10-17 6:27 ` Heiko Schocher [this message]
2013-10-16 4:53 ` [U-Boot] [PATCH 2/3] m68k: eliminate warnings in do_bootm_linux function Masahiro Yamada
2013-10-16 4:53 ` [U-Boot] [PATCH 3/3] m68k: eliminate a warning in cpu_init Masahiro Yamada
2014-06-19 15:19 ` [U-Boot] [U-Boot,3/3] " Tom Rini
2013-10-16 7:41 ` [U-Boot] [PATCH 0/3] All M68K boards are broken Albert ARIBAUD
2013-10-16 8:20 ` Masahiro Yamada
2013-10-16 8:43 ` Albert ARIBAUD
2013-10-16 9:14 ` Masahiro Yamada
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=525F8364.70506@denx.de \
--to=hs@denx.de \
--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