mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Christoph Hellwig <hch@infradead.org>,
	linux-kernel@vger.kernel.org,
	Eyal Lebedinsky <eyal@eyal.emu.id.au>
Subject: Re: 2.4.19pre8aa2
Date: Sun, 5 May 2002 02:25:08 +0200	[thread overview]
Message-ID: <20020505022508.J1260@dualathlon.random> (raw)
In-Reply-To: <20020504165440.C1260@dualathlon.random> <20020504160235.A14926@infradead.org>

On Sat, May 04, 2002 at 04:02:35PM +0100, Christoph Hellwig wrote:
> On Sat, May 04, 2002 at 04:54:40PM +0200, Andrea Arcangeli wrote:
> > Only in 2.4.19pre8aa2: 00_comx-driver-compile-1
> > 
> > 	Export proc_get_inode for kernel/drivers/net/wan/comx.o so
> > 	it can link as a module, noticed by Eyal Lebedinsky.
> 
> Don't do this - proc_get_inode is static for a reason and doing this
> export in the SuSE tree for ages doesn't make it any better.
> 
> The driver needs serious fixing instead.

I see the driver would better not use procfs that way, but as far I can
tell it's a clean-desing problem, not a pratical problem so I documented
it with a quite explicit name of the patch (and I don't recommend to
merge it in any monolithic tree out there were it could be forgotten, at
the very least it'd need a bold comment on it) and I'll backout as soon
as the driver is fixed. It seems Al started working on it on top of
2.4.5-ac16 on 22 Jun 2001 and after one year the proc_get_inode is still
there so I don't buy the argument that by not exporting it the driver
gets fixed faster, it just remains unusable as module it seems. the
important thing is that it doesn't get forgotten and the name of the
patch ensures that from my part.

Andrea

  parent reply	other threads:[~2002-05-05  0:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-04 14:54 2.4.19pre8aa2 Andrea Arcangeli
2002-05-04 15:02 ` 2.4.19pre8aa2 Christoph Hellwig
2002-05-04 23:34   ` 2.4.19pre8aa2 Eyal Lebedinsky
2002-05-05  3:04     ` 2.4.19pre8aa2 Keith Owens
2002-05-05  7:40       ` 2.4.19pre8aa2 Eyal Lebedinsky
2002-05-05  8:04         ` 2.4.19pre8aa2 Keith Owens
2002-05-05  8:16           ` 2.4.19pre8aa2 Keith Owens
2002-05-05 13:38           ` 2.4.19pre8aa2 Eyal Lebedinsky
2002-05-05  0:25   ` Andrea Arcangeli [this message]
2002-05-04 18:56 ` 2.4.19pre8aa2 Francois Romieu
2002-05-05  0:14   ` 2.4.19pre8aa2 Andrea Arcangeli
2002-05-08  2:27 ` 2.4.19pre8aa2 Pozsar Balazs
2002-05-08  9:34   ` 2.4.19pre8aa2 Andrea Arcangeli
2002-05-08  9:46     ` Problems with mm on Alpha Oliver Pitzeier
2002-05-08 10:54       ` Ivan Kokshaysky

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=20020505022508.J1260@dualathlon.random \
    --to=andrea@suse.de \
    --cc=eyal@eyal.emu.id.au \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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®