public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-omap@vger.kernel.org
Subject: Re: [patch 2.6.28-rc2-omap] H4: fix i2c registration
Date: Thu, 13 Nov 2008 13:43:02 -0800	[thread overview]
Message-ID: <20081113214302.GG3106@atomide.com> (raw)
In-Reply-To: <200811010038.05711.david-b@pacbell.net>

* David Brownell <david-b@pacbell.net> [081101 00:38]:
> From: David Brownell <dbrownell@users.sourceforge.net>
> 
> Registering the I2C devices on H4 boards once is enough;
> remove the extra call.
> 
> Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
> ---
> Mainline doesn't have the call to register the I2C adapter
> along with its devices ... this has that call *plus* the call
> to register just the board_info.  Seems to be the only OMAP2/3
> board with this bug.

Pushing to l-o, not adding to upstream queue.

Tony

> 
>  arch/arm/mach-omap2/board-h4.c |    3 ---
>  1 file changed, 3 deletions(-)
> 
> --- a/arch/arm/mach-omap2/board-h4.c
> +++ b/arch/arm/mach-omap2/board-h4.c
> @@ -746,9 +746,6 @@ static void __init omap_h4_init(void)
>  	/* Menelaus interrupt */
>  	omap_cfg_reg(W19_24XX_SYS_NIRQ);
>  
> -	i2c_register_board_info(1, h4_i2c_board_info,
> -			ARRAY_SIZE(h4_i2c_board_info));
> -
>  	platform_add_devices(h4_devices, ARRAY_SIZE(h4_devices));
>  	omap_board_config = h4_config;
>  	omap_board_config_size = ARRAY_SIZE(h4_config);
> --
> 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

      reply	other threads:[~2008-11-13 21:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-01  7:38 [patch 2.6.28-rc2-omap] H4: fix i2c registration David Brownell
2008-11-13 21:43 ` 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=20081113214302.GG3106@atomide.com \
    --to=tony@atomide.com \
    --cc=david-b@pacbell.net \
    --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