From: Mike Frysinger <vapier.adi@gmail.com>
To: Dave <kilroyd@googlemail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
a.p.zijlstra@chello.nl, tglx@linutronix.de,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:core/locking] locking: Check spinlock_t/rwlock_t argument type on non-SMP builds too
Date: Mon, 3 Aug 2009 23:05:34 -0400 [thread overview]
Message-ID: <8bd0f97a0908032005j5de90db6yf81cee2a28adfb1e@mail.gmail.com> (raw)
In-Reply-To: <4A773FFF.7050106@gmail.com>
On Mon, Aug 3, 2009 at 15:52, Dave wrote:
> The statistics (2.6.31-rc4ish) show a strong preference for static inline:
>
> $ find include -name "*.h" | xargs grep "static inline" | wc -l
> 6461
>
> $ find include -name "*.h" | xargs grep "extern inline" | wc -l
> 2
>
> $ find arch -name "*.h" | xargs grep "extern inline" | wc -l
> 125
>
> $ find arch -name "*.h" | xargs grep "static inline" | wc -l
> 7058
>
> $ find arch -name "*.h" | xargs grep "extern inline" | sed
> "s?^\(.*\):.*\$?\1?" | sort | uniq
> arch/blackfin/include/asm/string.h
we do want 'extern inline' (i.e. gnu_inline) semantics with the
Blackfin string functions, but the current nest of defines (making all
forms of "inline" expand to "always_inline") makes it hard to do at
the moment.
-mike
prev parent reply other threads:[~2009-08-04 3:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 18:44 [PATCH] check spinlock_t/rwlock_t argument type on non-SMP builds David Kilroy
2009-07-03 7:38 ` Ingo Molnar
2009-07-03 19:02 ` Dave
2009-07-18 12:14 ` Ingo Molnar
2009-07-22 18:11 ` [PATCH v2] " David Kilroy
2009-08-02 13:14 ` [tip:core/locking] locking: Check spinlock_t/rwlock_t argument type on non-SMP builds too tip-bot for David Kilroy
2009-08-02 13:40 ` Ingo Molnar
2009-08-02 16:45 ` Dave
2009-08-02 18:05 ` Ingo Molnar
2009-08-02 18:41 ` [PATCH v3] locking: check " David Kilroy
2009-08-02 19:30 ` [tip:core/locking] locking: Check " tip-bot for David Kilroy
2009-08-03 11:39 ` Ingo Molnar
2009-08-03 19:52 ` Dave
2009-08-04 3:05 ` Mike Frysinger [this message]
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=8bd0f97a0908032005j5de90db6yf81cee2a28adfb1e@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=hpa@zytor.com \
--cc=kilroyd@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®