From: Patrick McHardy <kaber@trash.net>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter-devel@vger.kernel.org,
Pablo Neira Ayuso <pablo@netfilter.org>,
Chris Friesen <chris.friesen@genband.com>
Subject: Re: [PATCH 3/3] netfilter: ipset: Fix compiler warnings "'hash_ip4_data_next' declared inline after being called"
Date: Mon, 11 Jul 2011 18:51:49 +0200 [thread overview]
Message-ID: <4E1B2A25.207@trash.net> (raw)
In-Reply-To: <1310377975-993-4-git-send-email-kadlec@blackhole.kfki.hu>
Am 11.07.2011 11:52, schrieb Jozsef Kadlecsik:
> Some gcc versions warn about prototypes without "inline" when the declaration
> includes the "inline" keyword. The fix generates a false error message
> "marked inline, but without a definition" with sparse below 0.4.2.
>
> Signed-off-by: Chris Friesen <chris.friesen@genband.com>
> Signed-off-by: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Applied, thanks.
But please try to keep the subject lines to something like 72
characters, if it exceeds that amount by a lot its better to
put the exact warning inside the body.
next prev parent reply other threads:[~2011-07-11 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 9:52 [PATCH 0/3] ipset patches against nf-next Jozsef Kadlecsik
2011-07-11 9:52 ` [PATCH 1/3] netfilter: ipset: Make possible to hash some part of the data element only Jozsef Kadlecsik
2011-07-11 9:52 ` [PATCH 2/3] netfilter: ipset: hash:net,iface fixed to handle overlapping nets behind different interfaces Jozsef Kadlecsik
2011-07-11 9:52 ` [PATCH 3/3] netfilter: ipset: Fix compiler warnings "'hash_ip4_data_next' declared inline after being called" Jozsef Kadlecsik
2011-07-11 16:51 ` Patrick McHardy [this message]
2011-07-11 16:49 ` [PATCH 2/3] netfilter: ipset: hash:net,iface fixed to handle overlapping nets behind different interfaces Patrick McHardy
2011-07-11 16:48 ` [PATCH 1/3] netfilter: ipset: Make possible to hash some part of the data element only 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=4E1B2A25.207@trash.net \
--to=kaber@trash.net \
--cc=chris.friesen@genband.com \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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.