From: David Weinehall <tao@acc.umu.se>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
James Bottomley <James.Bottomley@steeleye.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix in-kernel genksyms for parisc symbols
Date: Mon, 30 Jun 2003 00:18:14 +0200 [thread overview]
Message-ID: <20030629221814.GQ17986@khan.acc.umu.se> (raw)
In-Reply-To: <Pine.LNX.4.44.0306252221320.10554-100000@chaos.tp1.ruhr-uni-bochum.de>
On Wed, Jun 25, 2003 at 10:22:09PM +0200, Kai Germaschewski wrote:
> On Wed, 25 Jun 2003, Rusty Russell wrote:
>
> > In message <1056410864.1826.57.camel@mulgrave> you write:
> > > The problem is that the parisc libgcc.a library contains symbols that
> > > look like $$mulI and the like, but genksyms doesn't think $ is legal for
> > > a function symbol, so they all get dropped from the output. This means
> > > that inserting almost any module on parisc taints the kernel because
> > > these symbols have no version.
> > >
> > > The fix (attached below) was to allow $ in an identifier in lex.l (and
> > > obviously to update the _shipped files as well, but my flex/bison seem
> > > to be rather different from the one they were generated with, so I'll
> > > leave that to whomever has the correct versions).
> >
> > Looks fine, but my flex is different, too. Kai?
>
> I merged it, will submit.
Could you divulge what version of flex you use, to simplify future
changes?
Regards: David Weinehall
--
/) David Weinehall <tao@acc.umu.se> /) Northern lights wander (\
// Maintainer of the v2.0 kernel // Dance across the winter sky //
\) http://www.acc.umu.se/~tao/ (/ Full colour fire (/
next prev parent reply other threads:[~2003-06-29 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 23:27 [PATCH] fix in-kernel genksyms for parisc symbols James Bottomley
2003-06-25 6:02 ` Rusty Russell
2003-06-25 20:22 ` Kai Germaschewski
2003-06-29 22:18 ` David Weinehall [this message]
2003-07-02 15:24 ` Kai Germaschewski
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=20030629221814.GQ17986@khan.acc.umu.se \
--to=tao@acc.umu.se \
--cc=James.Bottomley@steeleye.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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;
as well as URLs for NNTP newsgroup(s).