From: R.E.Wolff@bitwizard.nl (Rogier Wolff)
To: Brian Gerst <bgerst@didntduck.org>
Cc: Patrick van de Lageweg <patrick@bitwizard.nl>,
Andrew Morton <andrewm@uow.edu.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rogier Wolff <wolff@bitwizard.nl>,
Philipp Rumpf <prumpf@parcelfarce.linux.theplanet.co.uk>
Subject: Re: [PROPOSED PATCH] ATM refcount + firestream
Date: Fri, 27 Oct 2000 16:56:11 +0200 (MEST) [thread overview]
Message-ID: <200010271456.QAA04258@cave.bitwizard.nl> (raw)
In-Reply-To: <39F995E8.FE7324BA@didntduck.org> from Brian Gerst at "Oct 27, 2000 10:49:12 am"
Brian Gerst wrote:
> > > + struct module *owner;
> > > + struct module *owner;
> > > bix:/home/morton>
> >
> > We use it throught the fops_get/fops_put macros to in/decrease the mod
> > counter. See the definitions for those macros (include/linux/fs.h)
> >
> > Patrick
>
> This will break horribly if fops_put/get are changed to inlines instead
> of macros. They are only supposed to be used on struct file_operations.
Oh?
Anyway, we'll get nice warnings about wrong type of argument when that
happens.
I was the one who found the fops_get/put code useful as a guideline
and also in fact as the code to call.
So the question is: What is the defined interface for fops_get/put: Is
it "it's a macro that... " or is it "it's a function (possibly a macro
for efficiency) that.... "?
Roger.
P.S. Apologies for Patrick's bad quoting habits: He had to catch a
train and forgot to delete the rest of the quoted mail.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* Common sense is the collection of *
****** prejudices acquired by age eighteen. -- Albert Einstein ********
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-10-27 14:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-27 7:50 [PROPOSED PATCH] ATM refcount + firestream Patrick van de Lageweg
2000-10-27 11:49 ` Andrew Morton
2000-10-27 13:49 ` Brian Gerst
2000-10-27 14:34 ` Patrick van de Lageweg
2000-10-27 14:49 ` Brian Gerst
2000-10-27 14:56 ` Rogier Wolff [this message]
2000-10-28 13:15 ` Philipp Rumpf
2000-10-28 13:37 ` Brian Gerst
2000-10-28 13:53 ` Philipp Rumpf
2000-10-28 13:55 ` Brian Gerst
2000-10-28 15:05 ` Philipp Rumpf
2000-10-28 15:50 ` Brian Gerst
2000-10-28 16:10 ` Andrew Morton
2000-10-30 15:18 ` Philipp Rumpf
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=200010271456.QAA04258@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=andrewm@uow.edu.au \
--cc=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@bitwizard.nl \
--cc=prumpf@parcelfarce.linux.theplanet.co.uk \
--cc=wolff@bitwizard.nl \
/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