[PATCH] always inline alloc_perturb.

[Roland McGrath]

> Hi, 
> to fix build error we change inline to always_inline. OK to commit?

What's the actual effect on code generation?  The warnings I've seen for
this are because it had inlined, cloned, and outlined (so only the test was
inlined), which is probably optimal.  In general, unless there is a strong
demonstrated reason to force inlining, we should usually just drop the
inline keyword and let the compiler decide.

> 	* malloc/malloc.c (alloc_perturb, free_perturb):
> 	use __always inline.

Capitalize a sentence.  Typo: __always_inline.


Thanks,
Roland