From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Måns Rullgård" <mru@users.sourceforge.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Writing modules for 2.5
Date: 15 Apr 2003 12:35:14 +0100 [thread overview]
Message-ID: <1050406513.27745.32.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <yw1xllyc7yoz.fsf@zaphod.guide>
On Maw, 2003-04-15 at 13:05, Måns Rullgård wrote:
> Next question: what is the correct replacement for MOD_INC_USE_COUNT?
If you know the use count is already one there isnt one, jut use
MOD_INC_USE_COUNT and flame Rusty
If you can't prove the use count is already one for your own module
you have a problem (and did in 2.4 in truth). The layers try and
lock the layer below. So char drivers are locked by core code,
block drivers likewise, tty drivers and so on...
Most driver layers now have an owner: field in the file ops or other
structure they register
owner: THIS_MODULE,
(THIS_MODULE comes out currently in a non modular buils too)
next prev parent reply other threads:[~2003-04-15 12:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <yw1x7k9w9flm.fsf@zaphod.guide.suse.lists.linux.kernel>
2003-04-15 11:28 ` Andi Kleen
2003-04-15 12:00 ` Måns Rullgård
2003-04-15 12:05 ` Andi Kleen
2003-04-15 12:05 ` Måns Rullgård
2003-04-15 11:35 ` Alan Cox [this message]
2003-04-15 12:39 ` Måns Rullgård
2003-04-15 12:57 ` Russell King
2003-04-15 13:24 ` Dave Jones
2003-04-15 15:42 ` Måns Rullgård
2003-04-15 21:31 ` Russell King
2003-04-15 14:24 ` Alan Cox
2003-04-15 12:15 ` Andreas Henriksson
2003-04-15 12:30 ` Måns Rullgård
2003-04-15 12:58 ` Russell King
2003-04-15 11:15 Måns Rullgård
2003-04-15 14:24 ` Jonathan Corbet
2003-04-15 20:43 ` Sam Ravnborg
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=1050406513.27745.32.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@users.sourceforge.net \
/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®