DPDK patches and discussions
 help / color / mirror / Atom feed
From: Lewis Donzis <lew@perftech.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Change ether_addr to avoid conflict
Date: Wed, 24 Oct 2018 07:35:28 -0500	[thread overview]
Message-ID: <905F0B17-2987-4847-A054-C94501ACBC2D@perftech.com> (raw)

Please consider changing "struct ether_addr" in rte_ether.h to "struct rte_ether_addr", in order to avoid conflicts with the same structure name /usr/include/net/ethernet.h.

Sometimes, there is need to include /usr/include/net/ethernet.h, but it conflicts with the same structure name in rte_ether.h.  Was there a reason this structure wasn't given the standard rte_ prefix?

Thanks,
lew

             reply	other threads:[~2018-10-24 12:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24 12:35 Lewis Donzis [this message]
2018-10-24 16:11 ` Stephen Hemminger
  -- strict thread matches above, loose matches on Subject: below --
2018-10-21 15:39 Lewis Donzis
2018-10-22 15:06 ` Wiles, Keith
2018-10-23  8:37   ` Thomas Monjalon

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=905F0B17-2987-4847-A054-C94501ACBC2D@perftech.com \
    --to=lew@perftech.com \
    --cc=dev@dpdk.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).