From: Kevin Hilman <khilman@ti.com>
To: Daniel Mack <zonque@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
tony@atomide.com
Subject: Re: [PATCH] ARM: OMAP: Overo: remove illegal extra call to overo_ads7846_init()
Date: Fri, 17 Jun 2011 09:03:20 -0700 [thread overview]
Message-ID: <87r56sbg3b.fsf@ti.com> (raw)
In-Reply-To: <1308324110-21918-1-git-send-email-zonque@gmail.com> (Daniel Mack's message of "Fri, 17 Jun 2011 17:21:50 +0200")
Daniel Mack <zonque@gmail.com> writes:
> Signed-off-by: Daniel Mack <zonque@gmail.com>
Thanks for fixing this, I noticed this recently too.
Please add a descriptive changelog. For example, why is it duplcate?
where is it already done? what commit added the extra call, what
problems does it cause, etc.
Also, your subject says 'illegal', but it's not really illegal. It's just
wrong. :) "remove duplcate call to..." is enough.
Thanks,
Kevin
> ---
> arch/arm/mach-omap2/board-overo.c | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/board-overo.c b/arch/arm/mach-omap2/board-overo.c
> index 175e1ab..110475f 100644
> --- a/arch/arm/mach-omap2/board-overo.c
> +++ b/arch/arm/mach-omap2/board-overo.c
> @@ -568,7 +568,6 @@ static void __init overo_init(void)
> usb_musb_init(NULL);
> usbhs_init(&usbhs_bdata);
> overo_spi_init();
> - overo_ads7846_init();
> overo_init_smsc911x();
> overo_display_init();
> overo_init_led();
next prev parent reply other threads:[~2011-06-17 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 15:21 [PATCH] ARM: OMAP: Overo: remove illegal extra call to overo_ads7846_init() Daniel Mack
2011-06-17 16:03 ` Kevin Hilman [this message]
2011-06-17 16:17 ` [PATCH] ARM: OMAP: Overo: remove duplicate " Daniel Mack
2011-06-17 20:59 ` Kevin Hilman
2011-07-01 7:30 ` 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=87r56sbg3b.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=zonque@gmail.com \
/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