From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Patrick McHardy <kaber@trash.net>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
netfilter-devel@vger.kernel.org, Julian Anastasov <ja@ssi.bg>,
Simon Horman <horms@verge.net.au>
Subject: Re: [PATCH V2] ipvs: disable inline net_ipvs function with CONFIG_IP_VS not being set
Date: Wed, 25 Mar 2015 14:12:56 +0100 [thread overview]
Message-ID: <5512B458.8000403@6wind.com> (raw)
In-Reply-To: <CACna6rwMOJqRusrooUXKFk9HbVA4NqOY18fCTkqHyTvQA6O_bA@mail.gmail.com>
Le 25/03/2015 12:08, Rafał Miłecki a écrit :
> On 25 March 2015 at 11:25, Nicolas Dichtel <nicolas.dichtel@6wind.com> wrote:
[snip]
>> For me, it's a bit strange to have '#ifdef CONFIG_IP_VS' in a file specific
>> to
>> this module. This just fix your third party module.
>
> Will do. I was just thinking this header doesn't follow headers logic
> well and wanted to help.
>
The logic is to fix bug that are in-tree ;-)
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-03-25 13:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 8:53 [PATCH] ipvs: fix header inline net_ipvs function to work without CONFIG_IP_VS Rafał Miłecki
2015-03-25 9:03 ` Nicolas Dichtel
2015-03-25 9:17 ` [PATCH V2] ipvs: disable inline net_ipvs function with CONFIG_IP_VS not being set Rafał Miłecki
2015-03-25 10:25 ` Nicolas Dichtel
2015-03-25 11:08 ` Rafał Miłecki
2015-03-25 13:12 ` Nicolas Dichtel [this message]
2015-03-25 20:04 ` Julian Anastasov
2015-03-25 20:15 ` Rafał Miłecki
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=5512B458.8000403@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=zajec5@gmail.com \
/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.