DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH 0/6] make eth_dev_ops const
Date: Mon, 21 Mar 2016 10:53:23 -0700	[thread overview]
Message-ID: <1458582809-19628-1-git-send-email-stephen@networkplumber.org> (raw)

Newer driver seem not to have gotten the message that eth_dev_ops
structure should be const.

Stephen Hemminger (6):
  bonding: make eth_dev_ops const
  cxgbe: make eth_dev_ops const
  bnx2x: make eth_dev_ops const
  nfp: make eth_dev_ops const
  szedata: make eth_dev_ops const
  mpipe: make eth_dev_ops const

 drivers/net/bnx2x/bnx2x_ethdev.c           |  4 +--
 drivers/net/bonding/rte_eth_bond_pmd.c     | 38 +++++++++++------------
 drivers/net/bonding/rte_eth_bond_private.h |  2 +-
 drivers/net/cxgbe/cxgbe_ethdev.c           |  2 +-
 drivers/net/mpipe/mpipe_tilegx.c           |  2 +-
 drivers/net/nfp/nfp_net.c                  |  2 +-
 drivers/net/szedata2/rte_eth_szedata2.c    | 48 +++++++++++++++---------------
 7 files changed, 49 insertions(+), 49 deletions(-)

-- 
2.1.4

             reply	other threads:[~2016-03-21 17:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21 17:53 Stephen Hemminger [this message]
2016-03-21 17:53 ` [dpdk-dev] [PATCH 1/6] bonding: " Stephen Hemminger
2016-03-21 17:53 ` [dpdk-dev] [PATCH 2/6] cxgbe: " Stephen Hemminger
2016-03-21 17:53 ` [dpdk-dev] [PATCH 3/6] bnx2x: " Stephen Hemminger
2016-03-21 17:53 ` [dpdk-dev] [PATCH 4/6] nfp: " Stephen Hemminger
2016-03-21 17:53 ` [dpdk-dev] [PATCH 5/6] szedata: " Stephen Hemminger
2016-03-21 17:53 ` [dpdk-dev] [PATCH 6/6] mpipe: " Stephen Hemminger
2016-03-23 12:09 ` [dpdk-dev] [PATCH 0/6] " Bruce Richardson

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=1458582809-19628-1-git-send-email-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --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).