mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	irda-users@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	jgarzik@pobox.com, linux-net@vger.kernel.org
Subject: Re: [2.4 patch] fix via-ircc.c .text.exit error
Date: Mon, 26 Jan 2004 14:11:53 -0800	[thread overview]
Message-ID: <20040126221153.GA18733@bougret.hpl.hp.com> (raw)
In-Reply-To: <20040126210126.GG513@fs.tum.de>

On Mon, Jan 26, 2004 at 10:01:26PM +0100, Adrian Bunk wrote:
> On Mon, Jan 26, 2004 at 11:28:36AM -0800, Jean Tourrilhes wrote:
> >
> > 	Thanks you Adrian. Yes, I must confess that I never test
> > non-modular build (because it doesn't work).
> >...
> 
> Are you saying it might compile statically, but it won't work?
> 
> In this case, what about disallowing building it statically in the 
> Config.in?

	I never looked in details at those issues. Some people claim
it works, but personally I always had touble with driver init (double
initialisation). I don't want to disable it if some embedded people
depend on it (stable kernel => stable feature list).
	My "solution" was to totally rework the driver init (and stack
init) in 2.5.X and put ample warning on my web page "use static at
your own risk".

	Jean

      parent reply	other threads:[~2004-01-26 22:12 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-16 14:11 Linux 2.4.25-pre6 Marcelo Tosatti
2004-01-16 15:34 ` Maciej Soltysiak
2004-01-16 15:52   ` [PATCH 2.6] " Maciej Soltysiak
2004-01-16 18:14     ` Mike Fedyk
2004-01-16 18:25       ` [PATCH 2.6 FIXED] " Maciej Soltysiak
2004-01-20 21:25 ` Lukasz Trabinski
2004-01-20 21:41   ` Marcelo Tosatti
2004-01-21  6:47     ` Lukasz Trabinski
2004-01-21 10:53       ` Marcelo Tosatti
2004-01-21 11:28         ` Lukasz Trabinski
2004-01-21 11:54           ` David Woodhouse
2004-01-21 16:07             ` Lukasz Trabinski
2004-01-21 20:12               ` Marcelo Tosatti
2004-01-28 15:04                 ` David Woodhouse
2004-01-28 17:03                   ` Lukasz Trabinski
2004-02-02 22:24                   ` Lukasz Trabinski
     [not found]                 ` <Pine.LNX.4.58L.0401220929450.18938@logos.cnet>
     [not found]                   ` <Pine.LNX.4.58LT.0401221248560.11640@oceanic.wsisiz.edu.pl>
     [not found]                     ` <Pine.LNX.4.58L.0401221014510.18938@logos.cnet>
     [not found]                       ` <Pine.LNX.4.58LT.0401221334070.2772@oceanic.wsisiz.edu.pl>
2004-02-04 13:26                         ` Marcelo Tosatti
2004-02-04 18:45                           ` Lukasz Trabinski
2004-02-04 23:20                             ` Lukasz Trabinski
2004-01-21 11:01       ` Marcelo Tosatti
2004-01-21 11:07       ` David Woodhouse
2004-01-25  0:40 ` [2.4 patch] fix via-ircc.c .text.exit error Adrian Bunk
2004-01-26 19:28   ` Jean Tourrilhes
2004-01-26 21:01     ` Adrian Bunk
2004-01-26 21:02       ` David S. Miller
2004-01-26 21:42         ` Jean Tourrilhes
2004-01-26 22:11       ` Jean Tourrilhes [this message]

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=20040126221153.GA18733@bougret.hpl.hp.com \
    --to=jt@bougret.hpl.hp.com \
    --cc=bunk@fs.tum.de \
    --cc=irda-users@lists.sourceforge.net \
    --cc=jgarzik@pobox.com \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@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

all inboxes | Powered by JetHome®