public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phil Carmody <ext-phil.2.carmody@nokia.com>
To: ext Peter Huewe <PeterHuewe@gmx.de>
Cc: Russell King <linux@arm.linux.org.uk>,
	Catalin Marinas <catalin.marinas@arm.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm/include: Fix missing semicolon in module.h
Date: Thu, 17 Jun 2010 12:24:19 +0300	[thread overview]
Message-ID: <20100617092419.GI17639@pcarmody-desktop> (raw)
In-Reply-To: <201006161932.00542.PeterHuewe@gmx.de>

On 16/06/10 19:32 +0200, ext Peter Huewe wrote:
> From: Peter Huewe <peterhuewe@gmx.de>
> 
> This patch fixes a missing semicolon which introduced buildfailures [2] for
> almost every arm defconfig, introduced by patch cecaa4c6b [1]
> 
> This issue arises only if CONFIG_ARM_UNWIND is not set.
> 
> Signed-off-by: Peter Huewe <peterhuewe@gmx.de>

My bad, sorry. 

Acked-by: Phil Carmody <ext-phil.2.carmody@nokia.com>

> ---
> KernelVersion: linux-next-20100616
> References:
> [1] cecaa4c6b ARM: 6172/1: module - additional unwind tables for exit/devexit
> [2] http://kisskb.ellerman.id.au/kisskb/compiler/11/
> [3] http://kisskb.ellerman.id.au/kisskb/buildresult/2725882/
> 
>  arch/arm/include/asm/module.h |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/arm/include/asm/module.h b/arch/arm/include/asm/module.h
> index fcff0d2..cbb0bc2 100644
> --- a/arch/arm/include/asm/module.h
> +++ b/arch/arm/include/asm/module.h
> @@ -26,7 +26,7 @@ struct mod_arch_specific {
>  };
>  #else
>  struct mod_arch_specific {
> -}
> +};
>  #endif
>  
>  /*
> -- 
> 1.6.4.4

  reply	other threads:[~2010-06-17  9:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16 17:32 [PATCH] arm/include: Fix missing semicolon in module.h Peter Huewe
2010-06-17  9:24 ` Phil Carmody [this message]
2010-06-23 23:28   ` Peter Hüwe

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=20100617092419.GI17639@pcarmody-desktop \
    --to=ext-phil.2.carmody@nokia.com \
    --cc=PeterHuewe@gmx.de \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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