From: Takashi Iwai <tiwai@suse.de>
To: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
Cc: linux-kernel@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>,
Gerd Knorr <kraxel@bytesex.org>
Subject: Re: modprobe + request_module() deadlock
Date: Fri, 19 Nov 2004 12:10:15 +0100 [thread overview]
Message-ID: <s5hpt2aayco.wl@alsa2.suse.de> (raw)
In-Reply-To: <cnjr8v$dcu$1@sea.gmane.org>
At Fri, 19 Nov 2004 09:04:16 +0500,
Alexander E. Patrakov wrote:
>
> Takashi Iwai wrote:
>
> > Can we add a module dependency manually somehow?
>
> Yes, recommend the user to add something like this to /etc/modprobe.conf:
>
> install a modprobe -i a ; modprobe b ; true
>
> But IMHO Rusty should provide a way to specify those "recommended" install
> lines in the modules themselves (so that they finally go
> to /lib/modules/`uname -r`/modules.alias or a similar autogenerated file),
> like that's already done wih aliases and char-majors.
Well, how about to add a new marker in the driver code such as
MODULE_DEPENDS_ON("somemodule");
so that depmod can pick it up?
Takashi
next prev parent reply other threads:[~2004-11-19 11:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 22:29 modprobe + request_module() deadlock Johannes Stezenbach
2004-11-18 3:48 ` Rusty Russell
2004-11-18 13:55 ` Johannes Stezenbach
2004-11-18 19:05 ` Takashi Iwai
2004-11-19 4:04 ` Alexander E. Patrakov
2004-11-19 11:10 ` Takashi Iwai [this message]
2004-11-19 11:50 ` Gerd Knorr
2004-11-19 12:42 ` Alexander E. Patrakov
2004-11-21 8:39 ` Rusty Russell
2004-11-22 10:25 ` Gerd Knorr
2004-11-22 14:16 ` Johannes Stezenbach
2004-11-22 14:44 ` Gerd Knorr
2004-11-22 15:36 ` Johannes Stezenbach
2004-11-22 16:52 ` Gerd Knorr
2004-11-24 5:02 ` Rusty Russell
2004-11-24 12:11 ` Gerd Knorr
2004-11-25 16:03 ` Gerd Knorr
2004-11-26 0:34 ` Rusty Russell
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=s5hpt2aayco.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=kraxel@bytesex.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrakov@ums.usu.ru \
--cc=rusty@rustcorp.com.au \
/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.