mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Ismail Donmez <ismail@pardus.org.tr>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	Kyle Moffett <mrmacman_g4@mac.com>, Andrew Morton <akpm@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>,
	mchehab@infradead.org
Subject: Re: __STRICT_ANSI__ checks in headers
Date: Fri, 06 Oct 2006 09:26:22 +0100	[thread overview]
Message-ID: <1160123182.26064.140.camel@pmac.infradead.org> (raw)
In-Reply-To: <200610051116.12726.ismail@pardus.org.tr>

On Thu, 2006-10-05 at 11:16 +0300, Ismail Donmez wrote:
> The problem shows itself in the modpost, somehow __extension__ clause seems to 
> foobar module CRC. I am not yet successfull on making modpost ignore 
> __extension__ .
> 
> Any ideas appreciated. 

Something like this (and build with GENERATE_PARSER=1) _ought_ to do it,
but doesn't work:

diff --git a/scripts/genksyms/keywords.gperf b/scripts/genksyms/keywords.gperf
index c75e0c8..1c31f38 100644
--- a/scripts/genksyms/keywords.gperf
+++ b/scripts/genksyms/keywords.gperf
@@ -11,6 +11,7 @@ __attribute, ATTRIBUTE_KEYW
 __attribute__, ATTRIBUTE_KEYW
 __const, CONST_KEYW
 __const__, CONST_KEYW
+__extension__,EXTENSION_KEYW
 __inline, INLINE_KEYW
 __inline__, INLINE_KEYW
 __signed, SIGNED_KEYW
diff --git a/scripts/genksyms/parse.y b/scripts/genksyms/parse.y
index ca04c94..66ae413 100644
--- a/scripts/genksyms/parse.y
+++ b/scripts/genksyms/parse.y
@@ -60,6 +60,7 @@ remove_list(struct string_list **pb, str
 %token CONST_KEYW
 %token DOUBLE_KEYW
 %token ENUM_KEYW
+%token EXTENSION_KEYW
 %token EXTERN_KEYW
 %token FLOAT_KEYW
 %token INLINE_KEYW
@@ -269,7 +270,7 @@ cvar_qualifier_seq:
 
 cvar_qualifier:
 	CONST_KEYW | VOLATILE_KEYW | ATTRIBUTE_PHRASE
-	| RESTRICT_KEYW
+	| RESTRICT_KEYW | EXTENSION_KEYW
 		{ /* restrict has no effect in prototypes so ignore it */
 		  remove_node($1);
 		  $$ = $1;

-- 
dwmw2


  parent reply	other threads:[~2006-10-06  8:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200609150901.33644.ismail@pardus.org.tr>
2006-09-15  6:42 ` David Woodhouse
2006-09-15 13:27   ` Kyle Moffett
     [not found]     ` <200609211200.25214.ismail@pardus.org.tr>
2006-09-21  9:02       ` David Woodhouse
2006-09-21 12:53         ` Ismail Donmez
2006-09-28  7:03           ` Ismail Donmez
2006-09-28  7:06             ` David Woodhouse
2006-09-28  7:30               ` Ismail Donmez
2006-10-01  4:53                 ` Andrew Morton
2006-10-01  5:20                   ` Kyle Moffett
2006-10-01  7:34                     ` Ismail Donmez
2006-10-01  9:14                       ` Sam Ravnborg
2006-10-01 12:54                         ` Ismail Donmez
2006-10-05  8:16                         ` Ismail Donmez
2006-10-05  8:56                           ` Kyle Moffett
2006-10-06  8:26                           ` David Woodhouse [this message]
2006-10-07  7:17                             ` Kyle Moffett

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=1160123182.26064.140.camel@pmac.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=akpm@osdl.org \
    --cc=ismail@pardus.org.tr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=mrmacman_g4@mac.com \
    --cc=sam@ravnborg.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

all inboxes | Powered by JetHome®