From: Simon Richter <Simon.Richter@in.tum.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: kkeil@suse.de, kai.germaschewski@gmx.de,
isdn4linux@listserv.isdn4linux.de, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] drivers/isdn/: "extern inline" -> "static inline"
Date: Sun, 30 Oct 2005 15:44:52 +0100 [thread overview]
Message-ID: <4364DC64.5000103@in.tum.de> (raw)
In-Reply-To: <20051030004304.GQ4180@stusta.de>
[-- Attachment #1: Type: text/plain, Size: 233 bytes --]
Hi,
Adrian Bunk schrieb:
> "extern inline" doesn't make much sense.
In fact, it does[1], but not in this particular case.
Simon
[1] "if this function is not inlined, treat it as extern instead of
creating a copy in this TU".
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 374 bytes --]
next prev parent reply other threads:[~2005-10-30 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-30 0:43 [2.6 patch] drivers/isdn/: "extern inline" -> "static inline" Adrian Bunk
2005-10-30 14:44 ` Simon Richter [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-07 21:18 Adrian Bunk
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=4364DC64.5000103@in.tum.de \
--to=simon.richter@in.tum.de \
--cc=bunk@stusta.de \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=kai.germaschewski@gmx.de \
--cc=kkeil@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox