From: Rob Landley <rob@landley.net>
To: linux-kernel@vger.kernel.org
Subject: Status of CONFIG_FORCED_INLINING?
Date: Wed, 23 May 2007 15:10:52 -0400
User-Agent: KMail/1.9.1
Cc: Arjan van de Ven <arjan@linux.intel.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200705231510.52932.rob@landley.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 674
Lines: 14

I notice that feature-removal-schedule.txt has CONFIG_FORCED_INLINING 
scheduled to go away most of a year ago.  My question is what replaces it:

Does #define inline __always_inline become the new standard and uses of 
__always_inline be removed, or should all instances of "inline" either be 
removed or replaced with __always_inline?  (Or are there going to be two 
keywords meaning exactly the same thing going forward?)

Rob
-
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/