From: Tony Lindgren <tony@atomide.com>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: linux-omap@vger.kernel.org, Jarkko Nikula <jarkko.nikula@nokia.com>
Subject: Re: [2.6.29-rc5][PATCH 1/1] ARM: OMAP: BEAGLE: Remove dead code for CONFIG_I2C2_OMAP_BEAGLE
Date: Tue, 24 Feb 2009 13:46:10 -0800 [thread overview]
Message-ID: <20090224214610.GP26205@atomide.com> (raw)
In-Reply-To: <1235321248-5844-2-git-send-email-jarkko.nikula@nokia.com>
* Jarkko Nikula <jhnikula@gmail.com> [090222 08:44]:
> There is no CONFIG_I2C2_OMAP_BEAGLE in mainline and it is under removal
> in linux-omap also so remove this dead code now.
Thanks, adding to omap3-upstream queue.
Tony
> Signed-off-by: Jarkko Nikula <jarkko.nikula@nokia.com>
> ---
> arch/arm/mach-omap2/board-omap3beagle.c | 3 ---
> 1 files changed, 0 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/board-omap3beagle.c b/arch/arm/mach-omap2/board-omap3beagle.c
> index e39cd2c..e3c8628 100644
> --- a/arch/arm/mach-omap2/board-omap3beagle.c
> +++ b/arch/arm/mach-omap2/board-omap3beagle.c
> @@ -175,9 +175,6 @@ static int __init omap3_beagle_i2c_init(void)
> {
> omap_register_i2c_bus(1, 2600, beagle_i2c_boardinfo,
> ARRAY_SIZE(beagle_i2c_boardinfo));
> -#ifdef CONFIG_I2C2_OMAP_BEAGLE
> - omap_register_i2c_bus(2, 400, NULL, 0);
> -#endif
> /* Bus 3 is attached to the DVI port where devices like the pico DLP
> * projector don't work reliably with 400kHz */
> omap_register_i2c_bus(3, 100, NULL, 0);
> --
> 1.5.6.5
>
> --
> 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:[~2009-02-24 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-22 16:47 [2.6.29-rc5][PATCH 0/1] ARM: OMAP: BEAGLE: Remove dead code for CONFIG_I2C2_OMAP_BEAGLE Jarkko Nikula
2009-02-22 16:47 ` [2.6.29-rc5][PATCH 1/1] " Jarkko Nikula
2009-02-24 21:46 ` 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=20090224214610.GP26205@atomide.com \
--to=tony@atomide.com \
--cc=jarkko.nikula@nokia.com \
--cc=jhnikula@gmail.com \
--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 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.