All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: zwane@linuxpower.ca, linux-kernel@vger.kernel.org,
	hch@infradead.org, Kai Germaschewski <kai.germaschewski@gmx.de>,
	sfr@canb.auug.org.au, "Nemosoft Unv." <nemosoft@smcc.demon.nl>,
	davem@redhat.com
Subject: Re: SET_MODULE_OWNER?
Date: Tue, 08 Apr 2003 23:48:12 -0400	[thread overview]
Message-ID: <3E9397FC.8050000@pobox.com> (raw)
In-Reply-To: <20030409032537.547E32C06F@lists.samba.org>

Rusty Russell wrote:
> In message <3E937144.9090105@pobox.com> you write:
> 
>>Why don't you just let the maintainers apply the driver "cleanups" if 
>>they wish, or do not wish, like DaveM did.  Only when that is 
>>accomplished is it reasonable to consider moving SET_MODULE_OWNER -- and 
>>only then if other people do not need it's obvious utility.
> 
> 
> The please define when it should and should not be used, so everyone
> knows.

Use with structures that have an owner field, if you care about 
cross-version kernel source compatibility.


> Currently it seems to be:
> 
> /* This macro should be used on structures which had the owner field
>    added between 2.2 and 2.4, and not others. */
> 
> Is that correct?

No.  SET_MODULE_OWNER is useful regardless of kernel version, not just 
the restrictive set you define here.  Different vendors may implement 
SET_MODULE_OWNER with a different range of kernel versions, if they so 
choose. It's not restricted at all to when struct net_device gained an 
'owner' field.

Maybe think of it this way:  a source code hook whose implementation is 
free to change, as long as it functionally produces the desired result. 
    The in-kernel definition of the macro is only one of N implementations.

	Jeff




  reply	other threads:[~2003-04-09  3:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3E92515B.6030807@pobox.com>
2003-04-08 12:25 ` SET_MODULE_OWNER? Rusty Russell
2003-04-09  0:13   ` SET_MODULE_OWNER? David S. Miller
2003-04-09  1:03   ` SET_MODULE_OWNER? Jeff Garzik
2003-04-09  3:23     ` SET_MODULE_OWNER? Rusty Russell
2003-04-09  3:48       ` Jeff Garzik [this message]
2003-04-09 15:00   ` SET_MODULE_OWNER? Kai Germaschewski
     [not found] <3E93AA3D.4050104@pobox.com>
2003-04-09  5:27 ` SET_MODULE_OWNER? Rusty Russell
2003-04-07  6:47 SET_MODULE_OWNER? Rusty Russell
2003-04-07  8:17 ` SET_MODULE_OWNER? Christoph Hellwig
2003-04-07 18:29 ` SET_MODULE_OWNER? Jeff Garzik
2003-04-08  2:01   ` SET_MODULE_OWNER? Rusty Russell
2003-04-08  2:16     ` SET_MODULE_OWNER? Zwane Mwaikambo
2003-04-08  3:41       ` SET_MODULE_OWNER? Rusty Russell
2003-04-08  4:39         ` SET_MODULE_OWNER? Jeff Garzik
2003-04-09  0:46           ` SET_MODULE_OWNER? Rusty Russell
2003-04-09  2:32             ` SET_MODULE_OWNER? Jeff Garzik
2003-04-08  2:27     ` SET_MODULE_OWNER? Jeff Garzik
2003-04-08  3:46       ` SET_MODULE_OWNER? Rusty Russell
2003-04-08  6:00         ` SET_MODULE_OWNER? Christoph Hellwig
2003-04-08 11:51         ` SET_MODULE_OWNER? Alan Cox
2003-04-08 14:46           ` SET_MODULE_OWNER? Jamie Lokier
2003-04-08 15:12             ` SET_MODULE_OWNER? Jeff Garzik
2003-04-08 16:45               ` SET_MODULE_OWNER? Jamie Lokier
2003-04-08 17:19                 ` SET_MODULE_OWNER? Jeff Garzik

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=3E9397FC.8050000@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=davem@redhat.com \
    --cc=hch@infradead.org \
    --cc=kai.germaschewski@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nemosoft@smcc.demon.nl \
    --cc=rusty@rustcorp.com.au \
    --cc=sfr@canb.auug.org.au \
    --cc=zwane@linuxpower.ca \
    /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.