mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Francois Romieu <romieu@cogenit.fr>
Cc: linux-kernel@vger.kernel.org, Eyal Lebedinsky <eyal@eyal.emu.id.au>
Subject: Re: 2.4.19pre8aa2
Date: Sun, 5 May 2002 02:14:00 +0200	[thread overview]
Message-ID: <20020505021400.I1260@dualathlon.random> (raw)
In-Reply-To: <20020504165440.C1260@dualathlon.random> <20020504205653.A27564@fafner.intra.cogenit.fr>

On Sat, May 04, 2002 at 08:56:53PM +0200, Francois Romieu wrote:
> Andrea Arcangeli <andrea@suse.de> :
> [...]
> > 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.
> 
> http://www.cs.Helsinki.FI/linux/linux-kernel/2001-24/0984.html may be of
> interest.

I also mentioned it would been cleaner if the driver design would be
changed not to use procfs that way. I will back it out as soon as the
driver will stop using it, it's not a change in a monolithic kernel
where it could be forgotten like an -ac or a mainline, it's in a
separate patch called 00_comx-driver-compile-1 so there's no risk to
forget about it.  It cannot hurt anybody to export it until the driver
design is changed to be cleaner, just don't use it in the meantime, if
you use it again in another driver that's your mistake not mine. It is
not a pratical problem (the pratical problem infact happens without the
00_comx-driver-compile-1 patch), it is only a documentation problem and
I think the name of the patch should be clear enough in that sense.

Andrea

  reply	other threads:[~2002-05-05  0:13 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   ` 2.4.19pre8aa2 Andrea Arcangeli
2002-05-04 18:56 ` 2.4.19pre8aa2 Francois Romieu
2002-05-05  0:14   ` Andrea Arcangeli [this message]
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=20020505021400.I1260@dualathlon.random \
    --to=andrea@suse.de \
    --cc=eyal@eyal.emu.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=romieu@cogenit.fr \
    /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®