All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
	Marcel Holtmann <marcel@holtmann.org>,
	Simon Kelley <simon@thekelleys.org.uk>
Subject: Re: [OOPS/HACK] atmel_cs and the latest changes in sysfs/symlink.c
Date: Mon, 26 Apr 2004 07:26:47 -0500	[thread overview]
Message-ID: <200404260726.47571.dtor_core@ameritech.net> (raw)
In-Reply-To: <20040425235844.E13748@flint.arm.linux.org.uk>

On Sunday 25 April 2004 05:58 pm, Russell King wrote:
> On Sun, Apr 25, 2004 at 04:53:53PM -0500, Dmitry Torokhov wrote:
> > On Friday 23 April 2004 03:39 pm, Russell King wrote:
> > > On Fri, Apr 23, 2004 at 10:14:24PM +0200, Marcel Holtmann wrote:
> > > > should we apply the pcmcia_get_sys_device() patch from Dmitry for now to
> > > > fix the current drivers that need a device for loading the firmware?
> > > 
> > > I don't think so - it obtains the struct device for the bridge itself
> > > which has nothing to do with the card inserted in the slot.
> > > 
> > 
> > Yes, my bad... I wonder if something like the patch below could be useful
> > for now (although it created only one device entry even if card has multiple
> > functions so we really need another device for every function):
> 
> This breaks modular builds - pcmcia_bus_type is in ds.c which is a
> separate module.
>

Ok, then one question before I shut up - why is it exported if other modules
can not use it?

-- 
Dmitry

  parent reply	other threads:[~2004-04-26 12:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-23  6:42 [OOPS/HACK] atmel_cs and the latest changes in sysfs/symlink.c Dmitry Torokhov
2004-04-23 12:25 ` Marcel Holtmann
2004-04-23 13:02   ` Dmitry Torokhov
2004-04-23 14:26     ` Marcel Holtmann
2004-04-23 16:55       ` Dmitry Torokhov
2004-04-23 17:16         ` Greg KH
2004-04-23 18:50           ` Marcel Holtmann
2004-04-23 19:46             ` Greg KH
2004-04-23 20:35           ` Russell King
2004-04-23 21:02             ` Marcel Holtmann
2004-04-23 15:31     ` Greg KH
2004-04-23 17:19       ` Greg KH
2004-04-23 18:03         ` Greg KH
2004-04-24  6:44           ` Dmitry Torokhov
2004-04-25  2:49             ` Greg KH
2004-04-25 21:48               ` Dmitry Torokhov
2004-05-04 21:04                 ` Greg KH
2004-05-05  7:08                   ` Dmitry Torokhov
2004-05-07 23:25                     ` Greg KH
2004-04-26 10:19           ` Vojtech Pavlik
2004-04-23 19:55   ` Russell King
2004-04-23 20:14     ` Marcel Holtmann
2004-04-23 20:39       ` Russell King
2004-04-25 21:53         ` Dmitry Torokhov
2004-04-25 22:58           ` Russell King
2004-04-26 10:35             ` Marcel Holtmann
2004-04-26 12:32               ` Dmitry Torokhov
2004-04-26 13:09                 ` Marcel Holtmann
2004-04-27  5:57                   ` Dmitry Torokhov
2004-04-26 12:26             ` Dmitry Torokhov [this message]
2004-04-23 15:28 ` Greg KH

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=200404260726.47571.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    --cc=simon@thekelleys.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.