DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH v2 0/2] add includes to help when editing in Eclipse
Date: Wed, 15 Jun 2022 18:10:11 +0100	[thread overview]
Message-ID: <20220615171013.36426-1-bruce.richardson@intel.com> (raw)
In-Reply-To: <20220614122904.159946-1-bruce.richardson@intel.com>

These two small patches add in some additional header includes to 3 DPDK
files, in order to improve the experience of anyone who, like me,
sometimes uses eclipse-cdt as an editor for working with DPDK code.
The C indexer in eclipse seems easily confused when missing some of
our macro definitions, so we can reduce that confusion by ensuring
that we include all needed headers to get those definitions.

V2: fix copy-paste error

Bruce Richardson (2):
  examples/l3fwd: add include for macro definition
  common/cnxk: add include for macro definition

 drivers/common/cnxk/roc_io.h         | 2 ++
 examples/l3fwd/l3fwd_em.h            | 2 ++
 examples/l3fwd/l3fwd_em_sequential.h | 2 ++
 3 files changed, 6 insertions(+)

--
2.34.1


  parent reply	other threads:[~2022-06-15 17:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 12:29 [PATCH " Bruce Richardson
2022-06-14 12:29 ` [PATCH 1/2] examples/l3fwd: add include for macro definition Bruce Richardson
2022-06-14 12:29 ` [PATCH 2/2] common/cnxk: " Bruce Richardson
2022-06-15  7:06   ` Thomas Monjalon
2022-06-15 10:15     ` Bruce Richardson
2022-06-15 17:10 ` Bruce Richardson [this message]
2022-06-15 17:10   ` [PATCH v2 1/2] examples/l3fwd: " Bruce Richardson
2022-06-26  8:35     ` Thomas Monjalon
2022-06-15 17:10   ` [PATCH v2 2/2] common/cnxk: " Bruce Richardson
2022-06-17 13:18     ` Jerin Jacob

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=20220615171013.36426-1-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.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).