mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Modules and the Interfaces who Love Them (Take I)
Date: Thu, 14 Nov 2002 11:28:57 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.44.0211141106200.2113-100000@serv> (raw)
In-Reply-To: <20021114032456.5676D2C0C9@lists.samba.org>

Hi,

On Thu, 14 Nov 2002, Rusty Russell wrote:

> Look, your implementation was slow, confusing, invasive, inflexible
> *and* buggy.

My patch was meant as demonstration, you reduce it to a single aspect - 
the module - driver interface.
The patch was intended to demonstrate more. First of all, how to fix the 
module mess without breaking everything. It demonstrated a way to 
introduce a new interface without breaking compability. The new driver 
interface on top of it was optional, it could also have been the old 
interface or your monster refs.

> I seriously question your taste in this matter.  You obviously hold a
> personal dislike for my code.   Fine.

Doing to the linking in the kernel is just plain wrong. Most of the module 
code could perfectly live in user space and it could be as simple as your 
kernel loader.

> > maybe I'm missing something, but it doesn't fix anything
> 
> Then you don't understand the problem.

Maybe you could explain, what problems it fixes, that justifies complete 
breakage?

bye, Roman


  parent reply	other threads:[~2002-11-14 10:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13 10:17 Rusty Russell
2002-11-13 19:02 ` Roman Zippel
2002-11-14  3:34   ` Rusty Russell
2002-11-14  4:34     ` Jeff Garzik
2002-11-14 10:28     ` Roman Zippel [this message]
2002-11-14 11:00     ` Roman Zippel

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=Pine.LNX.4.44.0211141106200.2113-100000@serv \
    --to=zippel@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@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®