From: Pavel Roskin <proski@gnu.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: hermes@gibson.dropbear.id.au,
orinoco-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linville@tuxdriver.com, jgarzik@pobox.com
Subject: Re: [2.6 patch] orinoco.h: "extern inline" -> "static __always_inline"
Date: Tue, 15 Aug 2006 15:26:33 -0400 [thread overview]
Message-ID: <1155669993.2063.4.camel@dv> (raw)
In-Reply-To: <20060815004046.GC3543@stusta.de>
On Tue, 2006-08-15 at 02:40 +0200, Adrian Bunk wrote:
> "extern inline" generates a warning with -Wmissing-prototypes and I'm
> currently working on getting the kernel cleaned up for adding this to
> the CFLAGS since it will help us to avoid a nasty class of runtime
> errors.
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
Thanks for the patch! I'm removing the last sentence in the comment as
irrelevant and fixing the comment. The patch is being sent to netdev by
StGIT, cc: author.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2006-08-15 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 0:40 [2.6 patch] orinoco.h: "extern inline" -> "static __always_inline" Adrian Bunk
2006-08-15 19:26 ` Pavel Roskin [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=1155669993.2063.4.camel@dv \
--to=proski@gnu.org \
--cc=bunk@stusta.de \
--cc=hermes@gibson.dropbear.id.au \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=orinoco-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).