All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Jay Vosburgh <fubar@us.ibm.com>,
	ctindel@users.sourceforge.net,
	bonding-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [2.6 patch] bonding.h: "extern inline" -> "static inline"
Date: Thu, 18 Jan 2007 22:07:31 -0500	[thread overview]
Message-ID: <45B035F3.1060303@garzik.org> (raw)
In-Reply-To: <20061212162439.GX28443@stusta.de>

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.
> 
> If there are places that really need a forced inline, __always_inline
> would be the correct solution.
> 
> Signed-off-by: Adrian Bunk <bunk@stusta.de>

applied



      reply	other threads:[~2007-01-19  3:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12 16:24 [2.6 patch] bonding.h: "extern inline" -> "static inline" Adrian Bunk
2007-01-19  3:07 ` Jeff Garzik [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=45B035F3.1060303@garzik.org \
    --to=jeff@garzik.org \
    --cc=bonding-devel@lists.sourceforge.net \
    --cc=bunk@stusta.de \
    --cc=ctindel@users.sourceforge.net \
    --cc=fubar@us.ibm.com \
    --cc=netdev@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.