From: Tony Lindgren <tony@atomide.com>
To: Koen Kooi <koen@openembedded.org>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP: board-omap3beagle: fix merge-damage in RTC code
Date: Fri, 16 May 2008 08:32:22 -0700 [thread overview]
Message-ID: <20080516153221.GD23002@atomide.com> (raw)
In-Reply-To: <1210836883-7409-1-git-send-email-koen@openembedded.org>
* Koen Kooi <koen@openembedded.org> [080515 00:36]:
> This patch fixes the merge-damage in the beagleboard RTC code
Heh, this should teach you to not trust me to merge patches manually! :)
Pushing today.
Tony
> Signed-off-by: Koen Kooi <koen@openembedded.org>
> ---
> arch/arm/mach-omap2/board-omap3beagle.c | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/board-omap3beagle.c b/arch/arm/mach-omap2/board-omap3beagle.c
> index 0c15ca0..0c0cbfc 100644
> --- a/arch/arm/mach-omap2/board-omap3beagle.c
> +++ b/arch/arm/mach-omap2/board-omap3beagle.c
> @@ -76,6 +76,7 @@ static struct platform_device *omap3_beagle_devices[] __initdata = {
>
> static void __init omap3_beagle_init(void)
> {
> + platform_add_devices(omap3_beagle_devices, ARRAY_SIZE(omap3_beagle_devices));
> omap_board_config = omap3_beagle_config;
> omap_board_config_size = ARRAY_SIZE(omap3_beagle_config);
> omap_serial_init();
> @@ -88,8 +89,6 @@ arch_initcall(omap3_beagle_i2c_init);
>
> static void __init omap3_beagle_map_io(void)
> {
> - platform_add_devices(omap3_beagle_devices,
> - ARRAY_SIZE(omap3_beagle_devices));
> omap2_set_globals_343x();
> omap2_map_common_io();
> }
> --
> 1.5.4.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-05-16 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 7:34 [PATCH] ARM: OMAP: board-omap3beagle: fix merge-damage in RTC code Koen Kooi
2008-05-16 15:32 ` Tony Lindgren [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=20080516153221.GD23002@atomide.com \
--to=tony@atomide.com \
--cc=koen@openembedded.org \
--cc=linux-omap@vger.kernel.org \
/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