From: mikpe@csd.uu.se
To: Russell King <rmk@arm.linux.org.uk>
Cc: Dominik Brodowski <linux@brodo.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.71 cardbus problem + possible solution
Date: Mon, 16 Jun 2003 16:38:52 +0200 [thread overview]
Message-ID: <16109.54908.249375.482633@gargle.gargle.HOWL> (raw)
In-Reply-To: <20030616153253.A13312@flint.arm.linux.org.uk>
Russell King writes:
> On Mon, Jun 16, 2003 at 03:25:16PM +0200, mikpe@csd.uu.se wrote:
> > 2.5.71 changed the name of the Yenta module from yenta_socket
> > to yenta. In my case (Latitude with RH9 user-space), this
> > prevented cardmgr from starting properly.
> >
> > Quick fix: add 'alias yenta_socket yenta' to /etc/modprobe.conf,
> > or s/yenta_socket/yenta/ in the appropriate config file (but
> > then you make multi-booting 2.4/2.5 more difficult).
>
> What do people want to do about this? I have no particular desire to
> answer all those emails asking about this, so unless Dominik objects,
> I think we should just rename "yenta.c" to "yenta_socket.c" so we have
> back-compatibility.
>
> (This issue has appeared because yenta_socket.ko used to be created
> by combining yenta.o with pci_socket.o. Since pci_socket.c no longer
> exists, we create the module from yenta.c directly, so its now called
> yenta.ko.)
I'd prefer compatibility, if there are no technical reasons for
breaking it. Reverting to the old name in 2.5.72 sounds like a
good idea.
next prev parent reply other threads:[~2003-06-16 14:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 13:25 mikpe
2003-06-16 14:32 ` Russell King
2003-06-16 14:38 ` mikpe [this message]
2003-06-16 14:53 ` Felipe Alfaro Solana
2003-06-16 14:58 ` Dominik Brodowski
2003-06-16 14:59 ` Russell King
2003-06-16 14:54 ` 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=16109.54908.249375.482633@gargle.gargle.HOWL \
--to=mikpe@csd.uu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=rmk@arm.linux.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 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®