Hi Microsoft team,

Can you please check Thomas's comment below regarding header licensing (of ip.h 
and in.h) and verify that it can be used in the dpdk project or do I need to 
change anything?

Headers are taken from: 
Ip.h: https://code.woboq.org/qt5/include/netinet/ip.h.html
In.h: https://code.woboq.org/qt5/include/netinet/in.h.html

> -----Original Message-----
> From: Thomas Monjalon <tho...@monjalon.net>
> Sent: Tuesday, June 16, 2020 12:04 PM
> To: Fady Bader <f...@mellanox.com>
> Cc: dev@dpdk.org; Tasnim Bashar <tbas...@mellanox.com>; Tal Shnaiderman
> <tal...@mellanox.com>; Yohad Tor <yoh...@mellanox.com>;
> dmitry.kozl...@gmail.com; harini.ramakrish...@microsoft.com;
> ocard...@microsoft.com; ranjit.me...@intel.com; olivier.m...@6wind.com
> Subject: Re: [dpdk-dev] [PATCH v2 3/3] eal/windows: librte_net build on
> Windows
> 
> 10/06/2020 14:00, Fady Bader:
> > +/* SPDX-License-Identifier: BSD-3-Clause
> > + * Copyright 2020 Mellanox Technologies, Ltd  */
> 
> Isn't it a different copyright?
> Where does it come from?
> 
> > +
> > +#ifndef _IN_H_
> > +#define _IN_H_
> > +
> > +#define IPPROTO_IP 0
> > +#define IPPROTO_HOPOPTS 0
> > +#define    IPPROTO_IPV4 4             /* IPv4 encapsulation */
> > +#define    IPPROTO_IPIP IPPROTO_IPV4  /* for compatibility */
> > +#define IPPROTO_TCP 6
> > +#define IPPROTO_UDP 17
> > +#define    IPPROTO_IPV6 41            /* IP6 header */
> > +#define    IPPROTO_ROUTING 43         /* IP6 routing header */
> > +#define    IPPROTO_FRAGMENT 44        /* IP6 fragmentation header */
> > +#define    IPPROTO_GRE 47             /* General Routing Encap. */
> > +#define    IPPROTO_ESP 50             /* IP6 Encap Sec. Payload */
> > +#define    IPPROTO_AH 51              /* IP6 Auth Header */
> > +#define IPPROTO_NONE 59            /* IPv6 no next header */
> > +#define    IPPROTO_DSTOPTS 60         /* IP6 destination option */
> > +#define IPPROTO_SCTP 132           /* Stream Control Transmission Protocol 
> > */
> 
> There are some tabs instead of space. Please double check.
> 

Reply via email to