Date: Thu, 22 May 2003 16:48:45 -0700 (PDT)
Message-Id: <20030522.164845.48515977.davem@redhat.com>
To: schlicht@uni-mannheim.de
Cc: akpm@digeo.com, mfc@krycek.org, linux-kernel@vger.kernel.org
Subject: Re: Error during compile of 2.5.69-mm8
From: "David S. Miller" <davem@redhat.com>
In-Reply-To: <200305230147.00730.schlicht@uni-mannheim.de>
References: <200305230128.06412.schlicht@uni-mannheim.de>
	<20030522.162913.115921853.davem@redhat.com>
	<200305230147.00730.schlicht@uni-mannheim.de>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 887
Lines: 23

   From: Thomas Schlichter <schlicht@uni-mannheim.de>
   Date: Fri, 23 May 2003 01:47:00 +0200
   
   There was a discussion about SET_MODULE_OWNER here on the list, once.
   You can find it here:

I know about it and in fact Rusty is the one that told me
to do what I did with SET_MODULE_OWNER.

FACT: SET_MODULE_OWNER() tracks how to set the module reference
      for a struct netdevice.

It always lived in netdevice.h and always served exactly this purpose.
So when I deleted ->owner from struct netdevice, SET_MODULE_OWNER
became a nop.

Therefore, it was a complete error for anyone else to start using this
macro for other structures.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/