All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Rajendra Nayak <rnayak@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/4] OMAP2: Fix compile breaks
Date: Tue, 5 Jan 2010 16:17:05 -0800	[thread overview]
Message-ID: <20100106001705.GJ14533@atomide.com> (raw)
In-Reply-To: <1260781959-28050-1-git-send-email-rnayak@ti.com>

Hi,

* Rajendra Nayak <rnayak@ti.com> [091214 01:11]:
> Fixes a couple of implicit function definition errors
> for functions defined only for omap3 and called in omap2/3
> common code, and one function argument mismatch.

Looks like this needs to be refreshed to apply. Also
please fix the few cosmetic issues below :)
 
> Signed-off-by: Rajendra Nayak <rnayak@ti.com>
> ---
>  arch/arm/mach-omap2/board-2430sdp.c |    2 +-
>  arch/arm/mach-omap2/serial.c        |    1 +
>  arch/arm/plat-omap/i2c.c            |    2 ++
>  3 files changed, 4 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/arm/mach-omap2/board-2430sdp.c b/arch/arm/mach-omap2/board-2430sdp.c
> index db9374b..dea1425 100644
> --- a/arch/arm/mach-omap2/board-2430sdp.c
> +++ b/arch/arm/mach-omap2/board-2430sdp.c
> @@ -147,7 +147,7 @@ static void __init omap_2430sdp_init_irq(void)
>  {
>  	omap_board_config = sdp2430_config;
>  	omap_board_config_size = ARRAY_SIZE(sdp2430_config);
> -	omap2_init_common_hw(NULL, NULL);
> +	omap2_init_common_hw(NULL, NULL, NULL, NULL, NULL);
>  	omap_init_irq();
>  	omap_gpio_init();
>  }
> diff --git a/arch/arm/mach-omap2/serial.c b/arch/arm/mach-omap2/serial.c
> index c067416..5c65d2d 100644
> --- a/arch/arm/mach-omap2/serial.c
> +++ b/arch/arm/mach-omap2/serial.c
> @@ -500,6 +500,7 @@ DEVICE_ATTR(sleep_timeout, 0644, sleep_timeout_show, sleep_timeout_store);
>  #define DEV_CREATE_FILE(dev, attr) WARN_ON(device_create_file(dev, attr))
>  #else
>  static inline void omap_uart_idle_init(struct omap_uart_state *uart) {}
> +static inline void omap_uart_block_sleep(struct omap_uart_state *uart){}

Should be like this for new entries:

static inline void omap_uart_block_sleep(struct omap_uart_state *uart)
{
}

Maybe also update the omap_uart_idle_init the same way?

  
> diff --git a/arch/arm/plat-omap/i2c.c b/arch/arm/plat-omap/i2c.c
> index fb447c1..f8eb3a0 100644
> --- a/arch/arm/plat-omap/i2c.c
> +++ b/arch/arm/plat-omap/i2c.c
> @@ -117,6 +117,8 @@ static void omap_i2c_set_wfc_mpu_wkup_lat(struct device *dev, int val)
>  {
>  	omap_pm_set_max_mpu_wakeup_lat(dev, val);
>  }
> +#else
> +static inline void omap_i2c_set_wfc_mpu_wkup_lat(struct device *dev, int val){}
>  #endif

Here too.

Regards,

Tony

      parent reply	other threads:[~2010-01-06  0:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14  9:12 [PATCH 1/4] OMAP2: Fix compile breaks Rajendra Nayak
2009-12-14  9:12 ` [PATCH 2/4] OMAP3: hwmod: add I2C hwmods for OMAP3430 Rajendra Nayak
2009-12-14  9:12   ` [PATCH 3/4] OMAP: I2C: split device registration; convert OMAP2+ to omap_device Rajendra Nayak
2009-12-14  9:12     ` [PATCH 4/4] OMAP3: I2C: Convert i2c driver to use omap_device/omap_hwmod Rajendra Nayak
2009-12-28 23:20     ` [PATCH 3/4] OMAP: I2C: split device registration; convert OMAP2+ to omap_device Tony Lindgren
2010-01-06  0:17 ` 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=20100106001705.GJ14533@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=rnayak@ti.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 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.