public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Dominik Brodowski <linux@brodo.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] pcmcia: bus pcmcia_bus_type, driver_socket as interface
Date: Mon, 24 Feb 2003 17:43:12 +0000	[thread overview]
Message-ID: <20030224174312.A9951@infradead.org> (raw)
In-Reply-To: <20030224162259.GA2277@brodo.de>; from linux@brodo.de on Mon, Feb 24, 2003 at 05:22:59PM +0100

On Mon, Feb 24, 2003 at 05:22:59PM +0100, Dominik Brodowski wrote:
> Hi!
> 
> Patch #1: pcmcia-2.5.62-bus_drivers-3
> These patches add a new bus_type pcmcia_bus_type, and registers all pcmcia
> drivers with this bus. This is still done using the "old" registration
> calls; but over the long term this will move -- so that the pcmcia core
> knows about module->owner, for example.
> 
> Patch #2: pcmcia-2.5.62-ds-1
> This starts a change of "Driver Servies" to become a "interface" to
> pcmcia_socket-class devices. The interface_add_data call is commented out
> due to a driver model bug (deadlock) Patrick Mochel already knows about. Due
> to this, removing a driver services module or a socket won't currently work.

This looks really nice!  Could you post an example driver converted to use
pcmcia_register_driver() and friends?


  reply	other threads:[~2003-02-24 17:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24 16:22 [RFC] pcmcia: bus pcmcia_bus_type, driver_socket as interface Dominik Brodowski
2003-02-24 17:43 ` Christoph Hellwig [this message]
2003-02-26 15:44   ` [PATCH] pcmcia: pcmcia_bus and pcmcia_driver [Was: Re: [RFC] pcmcia: bus pcmcia_bus_type, driver_socket as interface] Dominik Brodowski
2003-02-26 16:06   ` [PATCH] pcmcia: driver_socket as device_class interface " Dominik Brodowski

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=20030224174312.A9951@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@brodo.de \
    /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