Status of CONFIG_FORCED_INLINING?

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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: Status of CONFIG_FORCED_INLINING?
  - From: Arjan van de Ven <[email protected]>

Prev by Date: RE: [PATCH 1/2] Define new percpu interface for shared data -- version 3
Next by Date: [PATCH 1/4] AFS: Add TestSetPageError()
Previous by thread: [PATCH] headercheck: add dependency check and improve speed
Next by thread: Re: Status of CONFIG_FORCED_INLINING?
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]