From: Stephen Hemminger <stephen@networkplumber.org>
To: Baruch Siach <baruch@tkos.co.il>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] ip: include libc headers first
Date: Tue, 30 May 2017 17:31:51 -0700 [thread overview]
Message-ID: <20170530173151.771ea254@xeon-e3> (raw)
In-Reply-To: <8afdd8babb9e82bcfde78e851b24b698436a6f9f.1495459674.git.baruch@tkos.co.il>
On Mon, 22 May 2017 16:27:53 +0300
Baruch Siach <baruch@tkos.co.il> wrote:
> Including libc headers first helps as a workaround to redefinition of struct
> ethhdr with a suitably patched musl libc that suppresses the kernel
> if_ether.h.
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> ip/iplink_bridge.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/ip/iplink_bridge.c b/ip/iplink_bridge.c
> index 818b43c89b5b..cccdec1c203a 100644
> --- a/ip/iplink_bridge.c
> +++ b/ip/iplink_bridge.c
> @@ -13,9 +13,9 @@
> #include <stdlib.h>
> #include <string.h>
> #include <netinet/in.h>
> +#include <netinet/ether.h>
> #include <linux/if_link.h>
> #include <linux/if_bridge.h>
> -#include <netinet/ether.h>
> #include <net/if.h>
>
> #include "rt_names.h"
Applied.
Next time please fix the Subject line. You implied two patches by using 1/2
but only one was sent.
It is easier for me if you include iproute2 in subject since then it goes into a
separate folder.
Subject: [PATCH iproute2] ip: include libc headers first
or if intended for net-next
Subject: [PATCH iproute2 net-next] ip: add magic VRF support
next prev parent reply other threads:[~2017-05-31 0:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 13:27 [PATCH 1/2] ip: include libc headers first Baruch Siach
2017-05-22 13:27 ` [PATCH 2/2] Add missing <sys/types.h> include Baruch Siach
2017-05-22 17:24 ` Stephen Hemminger
2017-05-22 20:09 ` Baruch Siach
2017-05-22 20:23 ` Stephen Hemminger
2017-05-31 0:31 ` Stephen Hemminger [this message]
2017-05-31 20:59 ` [PATCH 1/2] ip: include libc headers first Baruch Siach
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=20170530173151.771ea254@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=baruch@tkos.co.il \
--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).