mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Christoph Hellwig <hch@infradead.org>,
	Gergely Madarasz <gorgo@itc.hu>,
	linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
	trivial@rustcorp.com.au
Subject: Re: [2.5 patch] let COMX depend on PROC_FS
Date: Sun, 8 Jun 2003 18:56:08 +0200	[thread overview]
Message-ID: <20030608165608.GI16164@fs.tum.de> (raw)
In-Reply-To: <20030608174908.A9377@infradead.org>

On Sun, Jun 08, 2003 at 05:49:08PM +0100, Christoph Hellwig wrote:
> On Sun, Jun 08, 2003 at 04:40:38PM +0200, Adrian Bunk wrote:
> > >From drivers/net/wan/comx.c:
> > 
> > <--  snip  -->
> > 
> > ...
> > #ifndef CONFIG_PROC_FS
> > #error For now, COMX really needs the /proc filesystem
> > #endif
> > ...
> > 
> > <--  snip  -->
> > 
> > 
> > The following patch add a dependency to Kconfig to avoid compile errors 
> > with CONFIG_COMX and !CONFIG_PROC_FS:
> 
> Actually it still doesn't link with this because the procfs code in it
> is utter crap and relies on a symbol proc_get_inode that isn't exported
> since 2.3.  As no one cared for this driver over years I'd suggest just
> removing it.

The proc_get_inode link problem only affects the modular build of 
comx.c .

The static build works fine in both 2.4 and 2.5.

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:[~2003-06-08 16:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-08 14:40 Adrian Bunk
2003-06-08 16:49 ` Christoph Hellwig
2003-06-08 16:56   ` Adrian Bunk [this message]
2003-06-08 16:58     ` Christoph Hellwig
2003-06-10 11:55       ` Pásztor Szilárd
2003-06-10 13:26         ` Christoph Hellwig
2003-06-10 13:51           ` Pásztor Szilárd
2003-06-10 13:57             ` Christoph Hellwig
2003-06-10 14:11               ` Pásztor Szilárd
2003-06-10 14:14           ` viro

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=20030608165608.GI16164@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=gorgo@itc.hu \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=trivial@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

all inboxes | Powered by JetHome®