From: David Miller <davem@davemloft.net>
To: ldv@altlinux.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] uapi: fix linux/mroute.h userspace compilation errors
Date: Sun, 19 Feb 2017 18:16:17 -0500 (EST) [thread overview]
Message-ID: <20170219.181617.818841385499874965.davem@davemloft.net> (raw)
In-Reply-To: <20170216150446.GC13804@altlinux.org>
From: "Dmitry V. Levin" <ldv@altlinux.org>
Date: Thu, 16 Feb 2017 18:04:46 +0300
> Include <linux/in.h> to fix the following linux/mroute.h userspace
> compilation errors:
>
> /usr/include/linux/mroute.h:58:18: error: field 'vifc_lcl_addr' has incomplete type
> struct in_addr vifc_lcl_addr; /* Local interface address */
> /usr/include/linux/mroute.h:61:17: error: field 'vifc_rmt_addr' has incomplete type
> struct in_addr vifc_rmt_addr; /* IPIP tunnel addr */
> /usr/include/linux/mroute.h:72:17: error: field 'mfcc_origin' has incomplete type
> struct in_addr mfcc_origin; /* Origin of mcast */
> /usr/include/linux/mroute.h:73:17: error: field 'mfcc_mcastgrp' has incomplete type
> struct in_addr mfcc_mcastgrp; /* Group in question */
> /usr/include/linux/mroute.h:84:17: error: field 'src' has incomplete type
> struct in_addr src;
> /usr/include/linux/mroute.h:85:17: error: field 'grp' has incomplete type
> struct in_addr grp;
> /usr/include/linux/mroute.h:109:17: error: field 'im_src' has incomplete type
> struct in_addr im_src,im_dst;
> /usr/include/linux/mroute.h:109:24: error: field 'im_dst' has incomplete type
> struct in_addr im_src,im_dst;
>
> Signed-off-by: Dmitry V. Levin <ldv@altlinux.org>
Applied.
prev parent reply other threads:[~2017-02-19 23:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170215200650.GG1028@altlinux.org>
2017-02-16 15:04 ` [PATCH v2] uapi: fix linux/mroute.h userspace compilation errors Dmitry V. Levin
2017-02-19 23:16 ` David Miller [this message]
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=20170219.181617.818841385499874965.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ldv@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).