linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Andreas Haumer <andreas@xss.co.at>,
	Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: [2.4 patch] disallow modular CONFIG_COMX
Date: Mon, 12 Jan 2004 17:24:49 -0500	[thread overview]
Message-ID: <40031EB1.5030705@pobox.com> (raw)
In-Reply-To: <20040111013043.GY25089@fs.tum.de>

Adrian Bunk wrote:
> On Wed, Dec 31, 2003 at 04:26:43PM +0100, Andreas Haumer wrote:
> 
>>...
>>Hi!
> 
> 
> Hi Andreas!
> 
> 
>>...
>>Here's a first report:
>>...
>>*) Unresolved symbol in kernel/drivers/net/wan/comx.o: proc_get_inode
>>...
> 
> 
> CONFIG_COMX=m always gave an unresolved symbol in kernel 2.4, and it
> seems noone is interested in properly fixing it.
> 
> The patch below disallows a modular CONFIG_COMX.

I agree with the intent...

At this point, I am tempted to simply comment it out of the Config.in, 
and let interested parties backport bug fixes and crap from 2.6 if they 
would like.  The driver has had obvious bugs for a while...

	Jeff




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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-31 13:13 Linux 2.4.24-pre3 Marcelo Tosatti
2003-12-31 13:53 ` Tim Cambrant
2003-12-31 15:26 ` Andreas Haumer
2004-01-10  1:39   ` [2.4 patch] fix CONFIG_DS1742 Config.in entry Adrian Bunk
2004-01-11  1:30   ` [2.4 patch] disallow modular CONFIG_COMX Adrian Bunk
2004-01-12 22:24     ` Jeff Garzik [this message]
2004-01-13  0:25       ` Adrian Bunk
2004-01-13  9:57       ` Christoph Hellwig
2004-01-13 10:51         ` viro
2004-01-12  2:10   ` [2.4 patch] simplify PARPORT_PC_PCMCIA dependencies Adrian Bunk
2004-01-13  0:58   ` [2.4 patch] simplify COMX_PROTO_LAPB dependencies Adrian Bunk
2003-12-31 18:51 ` Iostats reporting problems was: Linux 2.4.24-pre3 Mike Fedyk
2004-01-13  1:42   ` Rick Lindsley

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=40031EB1.5030705@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=andreas@xss.co.at \
    --cc=bunk@fs.tum.de \
    --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;
as well as URLs for NNTP newsgroup(s).