public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: SET_MODULE_OWNER?
Date: Wed, 09 Apr 2003 15:27:12 +1000	[thread overview]
Message-ID: <20030409053753.E613E2C06A@lists.samba.org> (raw)
In-Reply-To: Your message of "Wed, 09 Apr 2003 01:06:05 -0400." <3E93AA3D.4050104@pobox.com>

In message <3E93AA3D.4050104@pobox.com> you write:
> 
> looks ok to me

After months of intense negotiation, we have... a comment. 8)

Thanks Jeff.

Linus, please apply.
Rusty.

diff -urpN --exclude TAGS -X /home/rusty/devel/kernel/kernel-patches/current-dontdiff --minimal linux-2.5.67-bk1/include/linux/module.h working-2.5.67-bk1-set-owner/include/linux/module.h
--- linux-2.5.67-bk1/include/linux/module.h	2003-04-08 11:15:01.000000000 +1000
+++ working-2.5.67-bk1-set-owner/include/linux/module.h	2003-04-09 15:15:47.000000000 +1000
@@ -408,6 +408,12 @@ __attribute__((section(".gnu.linkonce.th
 #endif /* MODULE */
 
 #define symbol_request(x) try_then_request_module(symbol_get(x), "symbol:" #x)
+
+/* If you want backwards compat: some structs didn't have owner fields once */
+/* Think of SET_MODULE_OWNER like an IBM mainframe: leave it in a dark 
+   corner for years, don't break it, but don't ever upgrade it either :) 
+   If there is something newer and sexier than the mainframe, it's ok to 
+   use that instead.  The mainframe won't feel lonely. -- Jeff Garzik */
 #define SET_MODULE_OWNER(dev) ((dev)->owner = THIS_MODULE)
 
 /* BELOW HERE ALL THESE ARE OBSOLETE AND WILL VANISH */
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

       reply	other threads:[~2003-04-09  5:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3E93AA3D.4050104@pobox.com>
2003-04-09  5:27 ` Rusty Russell [this message]
     [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       ` SET_MODULE_OWNER? Jeff Garzik
2003-04-09 15:00   ` SET_MODULE_OWNER? Kai Germaschewski
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=20030409053753.E613E2C06A@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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