DPDK patches and discussions
 help / color / mirror / Atom feed
From: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
To: dev@dpdk.org
Cc: satishr@chelsio.com, indranil@chelsio.com
Subject: [dpdk-dev] [PATCH v2 0/4] net/cxgbe: fix build for Microsoft Windows OS support
Date: Wed, 19 Dec 2018 21:58:22 +0530	[thread overview]
Message-ID: <cover.1545236474.git.rahul.lakkireddy@chelsio.com> (raw)

This series of patches fix compilation warning and errors seen while
building CXGBE PMD in preparation for Microsoft Windows OS support.

Patch 1 uses relative paths for including header files.
Patch 2 fixes macros related to rte_log().
Patch 3 only redefines symbols when they are not available.
Patch 4 fixes other misc build issues.

Patches are generated against dpdk-next-net tree.

Build Environment:
1. Target OS: Microsoft Windows Server 2016
2. Compiler: Intel C++ Compiler v19 from Intel Parallel Studio XE 2019 [1]
3. Development Tools:
   3.1 Microsoft Visual Studio 2017 Professional
   3.2 Windows Software Development Kit (SDK) v10.0.17763
   3.3 Windows Driver Kit (WDK) v10.0.17763

[1] https://software.intel.com/en-us/parallel-studio-xe

Thanks,
Rahul

---
v2:
- Add more info in commit message regarding Windows build.

Rahul Lakkireddy (4):
  net/cxgbe: use relative paths for including header files
  net/cxgbe: fix macros related to logs for Windows
  net/cxgbe: only define symbols when not available
  net/cxgbe: fix other misc build issues for Windows

 drivers/net/cxgbe/Makefile         |  2 -
 drivers/net/cxgbe/base/adapter.h   |  4 +-
 drivers/net/cxgbe/base/common.h    |  4 +-
 drivers/net/cxgbe/base/t4_hw.c     |  4 +-
 drivers/net/cxgbe/base/t4vf_hw.c   |  2 +-
 drivers/net/cxgbe/clip_tbl.c       |  2 +-
 drivers/net/cxgbe/cxgbe.h          |  4 +-
 drivers/net/cxgbe/cxgbe_compat.h   | 83 ++++++++++++++++++++----------
 drivers/net/cxgbe/cxgbe_ethdev.c   |  2 +-
 drivers/net/cxgbe/cxgbe_filter.c   |  7 +--
 drivers/net/cxgbe/cxgbe_filter.h   |  2 +-
 drivers/net/cxgbe/cxgbe_flow.c     |  2 +-
 drivers/net/cxgbe/cxgbe_main.c     |  6 +--
 drivers/net/cxgbe/cxgbevf_ethdev.c |  2 +-
 drivers/net/cxgbe/cxgbevf_main.c   |  6 +--
 drivers/net/cxgbe/l2t.c            |  3 +-
 drivers/net/cxgbe/l2t.h            |  2 +-
 drivers/net/cxgbe/mps_tcam.h       |  2 +-
 drivers/net/cxgbe/sge.c            |  9 ++--
 19 files changed, 90 insertions(+), 58 deletions(-)

-- 
2.18.0

             reply	other threads:[~2018-12-19 16:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-19 16:28 Rahul Lakkireddy [this message]
2018-12-19 16:28 ` [dpdk-dev] [PATCH v2 1/4] net/cxgbe: use relative paths for including header files Rahul Lakkireddy
2018-12-19 16:28 ` [dpdk-dev] [PATCH v2 2/4] net/cxgbe: fix macros related to logs for Windows Rahul Lakkireddy
2018-12-19 16:28 ` [dpdk-dev] [PATCH v2 3/4] net/cxgbe: only define symbols when not available Rahul Lakkireddy
2018-12-19 16:28 ` [dpdk-dev] [PATCH v2 4/4] net/cxgbe: fix other misc build issues for Windows Rahul Lakkireddy
2018-12-19 21:39 ` [dpdk-dev] [PATCH v2 0/4] net/cxgbe: fix build for Microsoft Windows OS support Ferruh Yigit
2018-12-20  3:54   ` Rahul Lakkireddy

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=cover.1545236474.git.rahul.lakkireddy@chelsio.com \
    --to=rahul.lakkireddy@chelsio.com \
    --cc=dev@dpdk.org \
    --cc=indranil@chelsio.com \
    --cc=satishr@chelsio.com \
    /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).