public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.29-rc2
Date: Sat, 15 Jan 2005 21:50:02 +0100	[thread overview]
Message-ID: <20050115205002.GO4274@stusta.de> (raw)
In-Reply-To: <20050115114309.GA7397@logos.cnet>

On Sat, Jan 15, 2005 at 09:43:09AM -0200, Marcelo Tosatti wrote:
> 
> Hi Adrian!
> 
> On Sat, Jan 15, 2005 at 06:20:50AM +0100, Adrian Bunk wrote:
> > On Fri, Jan 14, 2005 at 11:55:55PM +0100, Steffen Moser wrote:
> > 
> > >...
> > >  - fsa01 (problem occurs):
> > >...
> > >  | modutils               2.4.5
> > >...
> > >  - gateway (no problem):
> > >...
> > >  | modutils               2.4.12
> > >....
> > 
> > OK, this seems to be the problem:
> > modutils before 2.4.10 don't know about EXPORT_SYMBOL_GPL.
> > 
> > Please upgrade modutils on fsa01 and report whether it fixes the 
> > problem.
> 
> Yes, thats the right solution - however I think it might be worth to have 
> the non-GPL versions. Several old distros ship modutils older than 2.4.10
> - eg SuSE Linux 7.1 (Oct 2001).
>...

Do a grep for EXPORT_SYMBOL_GPL in the 2.4.29-rc2 sources.

It seems for some reason people didn't scream in older 2.4 releases that 
already had the same problem in several places.

I see you have applied both my patch documenting modutils 2.4.10 was 
required and the EXPORT_SYMBOL_GPL -> EXPORT_SYMBOL patch for tty_io.c .

I don't like this mixed approach. IMHO, there are two clean solutions:
1. document modutils 2.4.10 was required, undo the EXPORT_SYMBOL_GPL -> 
   EXPORT_SYMBOL changes in tty_io.c
2. undo the EXPORT_SYMBOL_GPL -> EXPORT_SYMBOL changes in tty_io.c and
   change module.h to #define EXPORT_SYMBOL_GPL to EXPORT_SYMBOL

Both approaches have their obvious advantages and disadvantages, but 
they don't have the flaw that they special case tty_io.c .

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-01-15 20:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12 15:13 Linux 2.4.29-rc2 Marcelo Tosatti
2005-01-14 22:55 ` Steffen Moser
2005-01-14 23:17   ` Marcelo Tosatti
2005-01-15  2:58     ` David Dyck
2005-01-15  3:04       ` David Dyck
2005-01-15  5:23       ` Adrian Bunk
2005-01-15  6:39         ` David Dyck
2005-01-15  5:14     ` Adrian Bunk
2005-01-15  5:16       ` Adrian Bunk
2005-01-15  7:43     ` Arjan van de Ven
2005-01-15 10:07     ` Steffen Moser
2005-01-15  5:20   ` Adrian Bunk
2005-01-15 11:43     ` Marcelo Tosatti
2005-01-15 20:50       ` Adrian Bunk [this message]
2005-01-15 18:31         ` Marcelo Tosatti
2005-01-15 20:57         ` Jan Knutar

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=20050115205002.GO4274@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox