From: Andi Kleen <andi@firstfloor.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Frans Pop <elendil@planet.nl>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
isdn4linux@listserv.isdn4linux.de
Subject: Re: ISDN testing
Date: Mon, 21 Apr 2008 21:48:24 +0200 [thread overview]
Message-ID: <878wz76lbr.fsf@basil.nowhere.org> (raw)
In-Reply-To: <480CE960.4050000@garzik.org> (Jeff Garzik's message of "Mon, 21 Apr 2008 15:22:08 -0400")
Jeff Garzik <jeff@garzik.org> writes:
>
> Yeah, that's what my patchset does -- splits the "hisax" driver into
> multiple smaller drivers. Thus, "modprobe hisax" produces the results
> that you are seeing.
That will break a lot of user's setup.
> You'll need to determine which newly-created kernel module applies to
> your hardware. Let me know if you need help with that. The new
> drivers should be in
> /lib/modules/2.6.25-isdn/kernel/drivers/isdn/hisax/ provided that you
> enabled them in the kernel configuration.
One way to avoid that issue would be to continue having a dummy
"hisax" module that just depends on all the other drivers with
a symbol reference.
That could be optional with some compat CONFIG.
-Andi
next prev parent reply other threads:[~2008-04-21 19:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-20 22:39 [git patches] ISDN cleanups (modularization prep) Jeff Garzik
2008-04-21 0:05 ` ISDN testing (was: [git patches] ISDN cleanups (modularization prep)) Frans Pop
2008-04-21 1:43 ` ISDN testing Jeff Garzik
2008-04-21 13:36 ` Frans Pop
2008-04-21 19:22 ` Jeff Garzik
2008-04-21 19:48 ` Andi Kleen [this message]
2008-04-25 2:39 ` Jeff Garzik
2008-04-21 20:21 ` [git patches] ISDN cleanups (modularization prep) (was: ISDN testing) Frans Pop
2008-04-25 2:46 ` [git patches] ISDN cleanups (modularization prep) Jeff Garzik
2008-04-26 19:42 ` Frans Pop
2008-04-25 16:47 ` ISDN testing (was: [git patches] ISDN cleanups (modularization prep)) Jan Engelhardt
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=878wz76lbr.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=elendil@planet.nl \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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.