netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Christoph Paasch <christoph.paasch@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] iptables: avoid compile warnings for iptc_insert_chain
Date: Mon, 23 Mar 2009 13:51:34 +0100	[thread overview]
Message-ID: <49C785D6.3010604@trash.net> (raw)
In-Reply-To: <d69a2a7d86c4224396091673aefc59cf25d55713.1237460727.git.christoph.paasch@gmail.com>

Christoph Paasch wrote:
> iptc_insert_chain is too big to get inlined and so it generates
> a warning while compiling.

Applied, thanks. But please include the compiler messages in the
changelog when fixing warnings.

  reply	other threads:[~2009-03-23 12:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19  8:31 next iptables release Patrick McHardy
2009-03-19 10:01 ` Jan Engelhardt
2009-03-19 10:06   ` Patrick McHardy
2009-03-19 10:13 ` Jan Engelhardt
2009-03-19 11:01 ` Jan Engelhardt
2009-03-19 12:56   ` Patrick McHardy
2009-03-19 12:51 ` Pablo Neira Ayuso
2009-03-19 12:55   ` Patrick McHardy
2009-03-19 13:10     ` Pablo Neira Ayuso
2009-03-19 13:16       ` Patrick McHardy
2009-03-19 13:52         ` Jan Engelhardt
2009-03-19 13:56           ` Patrick McHardy
2009-03-19 13:45     ` Jan Engelhardt
2009-03-19 13:55       ` Patrick McHardy
2009-03-19 14:02         ` Jan Engelhardt
2009-03-19 14:08           ` Patrick McHardy
2009-03-20 13:24             ` Pablo Neira Ayuso
2009-03-20 14:25               ` Patrick McHardy
2009-03-19 13:55 ` [PATCH] iptables: avoid compile warnings for iptc_insert_chain Christoph Paasch
2009-03-23 12:51   ` Patrick McHardy [this message]
2009-03-21 14:46 ` next iptables release Jesper Dangaard Brouer
2009-03-23 13:09   ` Patrick McHardy

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=49C785D6.3010604@trash.net \
    --to=kaber@trash.net \
    --cc=christoph.paasch@gmail.com \
    --cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).