From: Andy Whitcroft <apw@shadowen.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
tglx@linutronix.de, nickpiggin@yahoo.com.au, mingo@redhat.com,
hpa@zytor.com, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: [PATCH v2] bitops kernel-doc: inline instead of macro
Date: Sat, 27 Oct 2007 15:30:29 +0100 [thread overview]
Message-ID: <20071027143029.GC5529@shadowen.org> (raw)
In-Reply-To: <20071027104328.GA5529@shadowen.org>
On Sat, Oct 27, 2007 at 11:43:28AM +0100, Andy Whitcroft wrote:
> On Thu, Oct 25, 2007 at 01:48:14PM -0700, Andrew Morton wrote:
>
> > Andy, I thought we were going to whine about __inline__ and __inline, too?
>
> Hmmm, I don't remember that coming up, but I'll add it to the todo. I
> am assuming plain 'inline' is preferred over both of these -- yell if
> you meant something else.
Ok, this will be in the next release and is in -next.
WARNING: plain inline is preferred over __inline
#4: FILE: tmp/testset-28768.c:1:
+static __inline int foo(void)
-apw
next prev parent reply other threads:[~2007-10-27 14:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 5:09 [PATCH] bitops kernel-doc: expand macro Randy Dunlap
2007-10-24 8:00 ` Nick Piggin
2007-10-24 15:38 ` Randy Dunlap
2007-10-25 16:31 ` [PATCH v2] bitops kernel-doc: inline instead of macro Randy Dunlap
2007-10-25 16:42 ` Thomas Gleixner
2007-10-25 16:55 ` Randy Dunlap
2007-10-25 17:05 ` Thomas Gleixner
2007-10-25 20:48 ` Andrew Morton
2007-10-25 21:21 ` [PATCH v3] " Randy Dunlap
2007-10-25 21:27 ` Thomas Gleixner
2007-10-25 21:27 ` [PATCH] x86 bitops: fix code style issues Randy Dunlap
2007-10-27 10:43 ` [PATCH v2] bitops kernel-doc: inline instead of macro Andy Whitcroft
2007-10-27 14:30 ` Andy Whitcroft [this message]
2007-10-27 18:48 ` H. Peter Anvin
2007-10-25 21:54 ` Nick Piggin
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=20071027143029.GC5529@shadowen.org \
--to=apw@shadowen.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nickpiggin@yahoo.com.au \
--cc=rdunlap@xenotime.net \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox