public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Xose Vazquez Perez <xose@wanadoo.es>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.23-pre5 bugs: depmod and Unresolved symbols
Date: Sat, 15 Nov 2003 22:18:18 +0100	[thread overview]
Message-ID: <20031115211818.GD9634@alpha.home.local> (raw)
In-Reply-To: <Pine.LNX.4.44.0311151428080.10014-100000@logos.cnet>

Hi,

On Sat, Nov 15, 2003 at 02:29:16PM -0200, Marcelo Tosatti wrote:
> 
> On Sat, 15 Nov 2003, Xose Vazquez Perez wrote:
> > http://ftp.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.23pre6aa3/00_comx-driver-compile-1
> > 
> > 00_comx-driver-compile-1 first appeared in 2.4.19pre8aa2 - 258 bytes
> > 
> > 	Export proc_get_inode for kernel/drivers/net/wan/comx.o so
> > 	it can link as a module, noticed by Eyal Lebedinsky.
> 
> I just applied this and Jeff Garzik pointed out that its wrong to export
> proc_get_inode, and that comx should be fixed instead.
> 
> I reverted the change. 

Christoph Hellwig once explained us why it was bad and basically what needed
to be done in comx to make it link. But I think that nobody uses this driver
nowadays or that its users blindly apply this patch. I myself once tried to
fix it because of this annoyance (although I don't use it), and found myself
duplicating lots of proc stuff so I concluded this was plain silly and that
the comx driver will simply be disabled in my later kernels.

Cheers,
Willy


      reply	other threads:[~2003-11-15 21:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-18 14:32 2.4.23-pre5 bugs: depmod and Unresolved symbols Xose Vazquez Perez
2003-11-15  1:01 ` Xose Vazquez Perez
2003-11-15 16:29   ` Marcelo Tosatti
2003-11-15 21:18     ` Willy Tarreau [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=20031115211818.GD9634@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=xose@wanadoo.es \
    /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