From: Tony Lindgren <tony@atomide.com>
To: Constantine Shulyupin <const@MakeLinux.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
Russell King <linux@arm.linux.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP2+: remove duplicated declaration of omap4430_init_late
Date: Fri, 26 Oct 2012 12:14:55 -0700 [thread overview]
Message-ID: <20121026191455.GQ11908@atomide.com> (raw)
In-Reply-To: <1351272589-9885-1-git-send-email-const@MakeLinux.com>
* Constantine Shulyupin <const@MakeLinux.com> [121026 10:31]:
> From: Constantine Shulyupin <const@MakeLinux.com>
>
> Problem:
> Function omap4430_init_late is declared twice in arch/arm/mach-omap2/common.h.
> Fix: remove out of order declaration, assuming all functions ordered accordingly processor number.
>
>
> Signed-off-by: Constantine Shulyupin <const@MakeLinux.com>
Thanks, applying into omap-for-v3.7-rc2/fixes-part2-take3.
Regards,
Tony
> ---
> arch/arm/mach-omap2/common.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/arm/mach-omap2/common.h b/arch/arm/mach-omap2/common.h
> index 7045e4d..45478d1 100644
> --- a/arch/arm/mach-omap2/common.h
> +++ b/arch/arm/mach-omap2/common.h
> @@ -152,7 +152,6 @@ void am33xx_init_early(void);
> void omap4430_init_early(void);
> void omap5_init_early(void);
> void omap3_init_late(void); /* Do not use this one */
> -void omap4430_init_late(void);
> void omap2420_init_late(void);
> void omap2430_init_late(void);
> void omap3430_init_late(void);
> --
> 1.7.9.5
>
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: remove duplicated declaration of omap4430_init_late
Date: Fri, 26 Oct 2012 12:14:55 -0700 [thread overview]
Message-ID: <20121026191455.GQ11908@atomide.com> (raw)
In-Reply-To: <1351272589-9885-1-git-send-email-const@MakeLinux.com>
* Constantine Shulyupin <const@MakeLinux.com> [121026 10:31]:
> From: Constantine Shulyupin <const@MakeLinux.com>
>
> Problem:
> Function omap4430_init_late is declared twice in arch/arm/mach-omap2/common.h.
> Fix: remove out of order declaration, assuming all functions ordered accordingly processor number.
>
>
> Signed-off-by: Constantine Shulyupin <const@MakeLinux.com>
Thanks, applying into omap-for-v3.7-rc2/fixes-part2-take3.
Regards,
Tony
> ---
> arch/arm/mach-omap2/common.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/arm/mach-omap2/common.h b/arch/arm/mach-omap2/common.h
> index 7045e4d..45478d1 100644
> --- a/arch/arm/mach-omap2/common.h
> +++ b/arch/arm/mach-omap2/common.h
> @@ -152,7 +152,6 @@ void am33xx_init_early(void);
> void omap4430_init_early(void);
> void omap5_init_early(void);
> void omap3_init_late(void); /* Do not use this one */
> -void omap4430_init_late(void);
> void omap2420_init_late(void);
> void omap2430_init_late(void);
> void omap3430_init_late(void);
> --
> 1.7.9.5
>
next prev parent reply other threads:[~2012-10-26 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 17:29 [PATCH] ARM: OMAP2+: remove duplicated declaration of omap4430_init_late Constantine Shulyupin
2012-10-26 17:29 ` Constantine Shulyupin
2012-10-26 19:14 ` Tony Lindgren [this message]
2012-10-26 19:14 ` Tony Lindgren
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=20121026191455.GQ11908@atomide.com \
--to=tony@atomide.com \
--cc=const@MakeLinux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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.