All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Govindraj.R" <govindraj.raja@ti.com>
Cc: linux-omap@vger.kernel.org, Benoit Cousson <b-cousson@ti.com>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: Re: [PATCH] OMAP2+: Fix Compilation error when omap_l3_noc built as module
Date: Fri, 18 Nov 2011 16:37:37 -0800	[thread overview]
Message-ID: <20111119003737.GB31337@atomide.com> (raw)
In-Reply-To: <1320839199-4006-1-git-send-email-govindraj.raja@ti.com>

* Govindraj.R <govindraj.raja@ti.com> [111109 03:12]:
> Fix below compilation failure on mainline kernel 3.2-rc1
> when omap_l3_noc.c is built as module.
> 
> arch/arm/mach-omap2/omap_l3_noc.c:240: error: expected ',' or ';' before 'MODULE_DEVICE_TABLE'
> 
> Signed-off-by: Govindraj.R <govindraj.raja@ti.com>
> Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>

Thanks applying into fixes.

Tony

> ---
>  arch/arm/mach-omap2/omap_l3_noc.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/arm/mach-omap2/omap_l3_noc.c b/arch/arm/mach-omap2/omap_l3_noc.c
> index 6a66aa5..d15225f 100644
> --- a/arch/arm/mach-omap2/omap_l3_noc.c
> +++ b/arch/arm/mach-omap2/omap_l3_noc.c
> @@ -237,7 +237,7 @@ static int __devexit omap4_l3_remove(struct platform_device *pdev)
>  static const struct of_device_id l3_noc_match[] = {
>  	{.compatible = "ti,omap4-l3-noc", },
>  	{},
> -}
> +};
>  MODULE_DEVICE_TABLE(of, l3_noc_match);
>  #else
>  #define l3_noc_match NULL
> -- 
> 1.7.4.1
> 

      reply	other threads:[~2011-11-19  0:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09 11:46 [PATCH] OMAP2+: Fix Compilation error when omap_l3_noc built as module Govindraj.R
2011-11-19  0:37 ` 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=20111119003737.GB31337@atomide.com \
    --to=tony@atomide.com \
    --cc=b-cousson@ti.com \
    --cc=govindraj.raja@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=santosh.shilimkar@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.