All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [genksyms patch 1/4] parser: fix the __attribute__ rule
Date: Wed, 30 Jul 2008 22:43:11 +0200	[thread overview]
Message-ID: <20080730204311.GA17287@uranus.ravnborg.org> (raw)
In-Reply-To: <20080721025912.739333284@suse.de>

On Mon, Jul 21, 2008 at 04:28:24AM +0200, Andreas Gruenbacher wrote:
> Gcc __attribute__ definitions may occur repeatedly, e.g.,
> 
> 	static int foo __attribute__((__used__))
> 		       __attribute__((aligned (16)));
> 
> The genksyms parser does not understand this, and generates a syntax error.
> Fix this case.
> 
> Signed-off-by: Andreas Gruenbacher <agruen@suse.de>

Can I ask you to update the _shipped files and resend the patch.
I have only bison 2.1 available on my box and
I do not want to downgrade when regenerating the bison files.

To do it just do a:
make clean
make allmodconfig
make GENERATE_PARSER=1 modules

Drop the other _shipped files that are not relevant
(keywords.c and lex.c).

	Sam

  reply	other threads:[~2008-07-30 20:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21  2:28 [genksyms patch 0/4] Checksum tracking and tweaking Andreas Gruenbacher
2008-07-21  2:28 ` [genksyms patch 1/4] parser: fix the __attribute__ rule Andreas Gruenbacher
2008-07-30 20:43   ` Sam Ravnborg [this message]
2008-07-30 22:03     ` Andreas Gruenbacher
2008-07-31 21:17       ` Sam Ravnborg
2008-07-21  2:28 ` [genksyms patch 2/4] Include extern information in dumps Andreas Gruenbacher
2008-07-31 21:18   ` Sam Ravnborg
2008-07-21  2:28 ` [genksyms patch 3/4] Track symbol checksum changes Andreas Gruenbacher
2008-09-03  5:02   ` Andrew Morton
2008-09-03  8:13     ` Andreas Gruenbacher
2008-07-21  2:28 ` [genksyms patch 4/4] Allow to ignore " Andreas Gruenbacher

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=20080730204311.GA17287@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=agruen@suse.de \
    --cc=linux-kernel@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 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.