From: Florian Weimer <fweimer@redhat•com>
To: Andreas Roeseler <andreas.a.roeseler@gmail•com>
Cc: netdev@vger•kernel.org, davem@davemloft•net,
yoshfuji@linux-ipv6•org, dsahern@kernel•org, kuba@kernel•org
Subject: Re: [PATCH net-next V6 1/6] icmp: add support for RFC 8335 PROBE
Date: Wed, 02 Jun 2021 20:51:43 +0200 [thread overview]
Message-ID: <87r1hkt800.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <48ff14c5fff0af909519619caa26d20fcda5159c.camel@gmail.com> (Andreas Roeseler's message of "Wed, 02 Jun 2021 13:46:32 -0500")
* Andreas Roeseler:
> Are <netinet/in.h> and <linux/in.h> the only conflicting files?
> <linux/in.h> is only included to gain use of the in_addr struct, but
> that can be easily substituted out of the code in favor of __be32.
> Therefore we would no longer need to include <linux/in.h> and would
> remove the conflict.
I'm not 100% sure, but it looks this way. I can include <netinet/in.h>
and both <linux/in6.h> and <linux/if.h> in the same translation unit.
Thanks,
Florian
next prev parent reply other threads:[~2021-06-02 18:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 1:45 [PATCH net-next V6 0/6] add support for RFC 8335 PROBE Andreas Roeseler
2021-03-30 1:45 ` [PATCH net-next V6 1/6] icmp: " Andreas Roeseler
2021-06-02 17:58 ` Florian Weimer
2021-06-02 18:46 ` Andreas Roeseler
2021-06-02 18:51 ` Florian Weimer [this message]
2021-03-30 1:45 ` [PATCH net-next V6 2/6] ICMPV6: " Andreas Roeseler
2021-03-30 1:45 ` [PATCH net-next V6 3/6] net: add sysctl for enabling RFC 8335 PROBE messages Andreas Roeseler
2021-03-30 1:45 ` [PATCH net-next V6 4/6] net: add support for sending " Andreas Roeseler
2021-03-30 1:45 ` [PATCH net-next V6 5/6] ipv6: add ipv6_dev_find to stubs Andreas Roeseler
2021-03-30 1:45 ` [PATCH net-next V6 6/6] icmp: add response to RFC 8335 PROBE messages Andreas Roeseler
2021-03-30 20:50 ` [PATCH net-next V6 0/6] add support for RFC 8335 PROBE patchwork-bot+netdevbpf
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=87r1hkt800.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat$(echo .)com \
--cc=andreas.a.roeseler@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=yoshfuji@linux-ipv6$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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