public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Adam Belay <ambx1@neo.rr.com>,
	linux@dominikbrodowski.de, akpm@osdl.org, rml@ximian.com,
	linux-kernel@vger.kernel.org, linux-pcmcia@lists.infradead.org
Subject: Re: [PATCH] pcmcia driver model support [1/5]
Date: Fri, 6 Aug 2004 11:47:08 +0100	[thread overview]
Message-ID: <20040806114708.B13653@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040805222026.GA11641@neo.rr.com>; from ambx1@neo.rr.com on Thu, Aug 05, 2004 at 10:20:26PM +0000

On Thu, Aug 05, 2004 at 10:20:26PM +0000, Adam Belay wrote:
> This patch set is an updated version from the last and is against
> 2.6.8-rc3.  It includes suggestions from Dominik and an independent
> pcmcia bugfix.  I would appreciate any comments.

I'm overall _NOT_ happy with the growing number of people trying to
"fix" PCMCIA to do what they want it to do.

I've recently had davem screaming and shouting his head off at me
while I was at OLS claiming that PCMCIA network drivers _MUST_ be
user unloadable at any time, irrespective of the requirements of
the PCMCIA layer.

It's _VERY_ easy to fuck up the PCMCIA code - we've fucked it up
several times already and the only way to detect these fuckups is
to change things _SLOWLY_ and let a full release cycle pass by
between changes.  Yes, it means that PCMCIA changes take _MONTHS_
but that's reality.

So please slow down.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

      reply	other threads:[~2004-08-06 10:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05 22:20 [PATCH] pcmcia driver model support [1/5] Adam Belay
2004-08-06 10:47 ` Russell King [this message]

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=20040806114708.B13653@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=akpm@osdl.org \
    --cc=ambx1@neo.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=linux@dominikbrodowski.de \
    --cc=rml@ximian.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