All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: linux-kernel@vger.kernel.org
Cc: Arjan van de Ven <arjan@linux.intel.com>
Subject: Status of CONFIG_FORCED_INLINING?
Date: Wed, 23 May 2007 15:10:52 -0400	[thread overview]
Message-ID: <200705231510.52932.rob@landley.net> (raw)

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

             reply	other threads:[~2007-05-23 19:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23 19:10 Rob Landley [this message]
2007-05-23 19:42 ` Status of CONFIG_FORCED_INLINING? Arjan van de Ven
2007-05-23 21:22   ` Adrian Bunk
2007-05-23 21:28     ` Roland Dreier
2007-05-24 12:38       ` Robert P. J. Day
2007-05-24 16:55         ` Rob Landley
2007-05-24 17:10       ` Adrian Bunk
2007-05-24 17:14         ` Roland Dreier
2007-05-24 17:47           ` Rob Landley
2007-05-24 17:47             ` Arjan van de Ven
2007-05-24 18:14               ` Rob Landley
2007-05-24 17:55             ` Roland Dreier
2007-05-24 18:07               ` Adrian Bunk
2007-05-24 18:32                 ` Roland Dreier
2007-05-24 22:41                   ` Adrian Bunk
2007-05-24 17:57           ` Adrian Bunk
2007-05-23 21:31     ` Arjan van de Ven
2007-05-24 17:12       ` Adrian Bunk
2007-05-24 16:29     ` Jan Engelhardt
2007-05-24 17:14       ` Adrian Bunk
2007-05-24 17:17         ` Arjan van de Ven
2007-05-24 17:40       ` Rob Landley

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=200705231510.52932.rob@landley.net \
    --to=rob@landley.net \
    --cc=arjan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.