From: "Arnaldo Carvalho de Melo" <acme@redhat.com>
To: Pavel Emelyanov <xemul@openvz.org>
Cc: David Miller <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>,
devel@openvz.org
Subject: Re: [PATCH] Clean the ip_sockglue.c from some ugly ifdefs
Date: Thu, 1 Nov 2007 14:31:13 -0200 [thread overview]
Message-ID: <20071101163112.GE13130@ghostprotocols.net> (raw)
In-Reply-To: <4729F642.7000709@openvz.org>
Em Thu, Nov 01, 2007 at 06:52:34PM +0300, Pavel Emelyanov escreveu:
> The #idfed CONFIG_IP_MROUTE is sometimes places inside the if-s,
> which looks completely bad. Similar ifdefs inside the functions
> looks a bit better, but they are also not recommended to be used.
>
> Provide an ifdef-ed ip_mroute_opt() helper to cleanup the code.
>
> Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
Perhaps a better name would be ip_mroute_valid_opt()?
- Arnaldo
next prev parent reply other threads:[~2007-11-01 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 15:52 [PATCH] Clean the ip_sockglue.c from some ugly ifdefs Pavel Emelyanov
2007-11-01 16:31 ` Arnaldo Carvalho de Melo [this message]
2007-11-01 16:38 ` Pavel Emelyanov
2007-11-06 5:32 ` David Miller
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=20071101163112.GE13130@ghostprotocols.net \
--to=acme@redhat.com \
--cc=davem@davemloft.net \
--cc=devel@openvz.org \
--cc=netdev@vger.kernel.org \
--cc=xemul@openvz.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).