From: Jiri Benc <jbenc@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org,
Steffen Klassert <steffen.klassert@secunet.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
James Chapman <jchapman@katalix.com>,
Paul Moore <paul@paul-moore.com>,
Pravin Shelar <pshelar@nicira.com>,
Johannes Berg <johannes@sipsolutions.net>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [PATCH net-next 2/4] xfrm: simplify xfrm_address_t use
Date: Tue, 7 Apr 2015 18:35:21 +0200 [thread overview]
Message-ID: <20150407183521.3a169d84@griffin> (raw)
In-Reply-To: <20150407182958.51a7b13f@griffin>
On Tue, 7 Apr 2015 18:29:58 +0200, Jiri Benc wrote:
> What could be done that should work with earlier glibc versions is
> including "utils.h" before <linux/xfrm.h> in xfrm_monitor.c. Could you
> try that? Would it be an acceptable workaround?
Or, better, include <netinet/in.h> before <linux/xfrm.h> in
xfrm_monitor.c to keep the order of inclusion of local and system
headers.
Jiri
--
Jiri Benc
next prev parent reply other threads:[~2015-04-07 16:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-29 14:59 [PATCH net-next 0/4] netlink: access functions for IP address attributes Jiri Benc
2015-03-29 14:59 ` [PATCH net-next 1/4] tcp: simplify inetpeer_addr_base use Jiri Benc
2015-03-29 14:59 ` [PATCH net-next 2/4] xfrm: simplify xfrm_address_t use Jiri Benc
2015-04-07 16:01 ` Stephen Hemminger
2015-04-07 16:29 ` Jiri Benc
2015-04-07 16:35 ` Jiri Benc [this message]
2015-03-29 14:59 ` [PATCH net-next 3/4] netlink: implement nla_put_in_addr and nla_put_in6_addr Jiri Benc
2015-03-29 14:59 ` [PATCH net-next 4/4] netlink: implement nla_get_in_addr and nla_get_in6_addr Jiri Benc
2015-03-29 19:02 ` [PATCH net-next 0/4] netlink: access functions for IP address attributes Johannes Berg
2015-03-31 17:58 ` 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=20150407183521.3a169d84@griffin \
--to=jbenc@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=jchapman@katalix.com \
--cc=johannes@sipsolutions.net \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=paul@paul-moore.com \
--cc=pshelar@nicira.com \
--cc=steffen.klassert@secunet.com \
--cc=stephen@networkplumber.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).