DPDK patches and discussions
 help / color / mirror / Atom feed
From: Helin Zhang <helin.zhang@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/2] remove registers for early hardware only
Date: Thu, 23 Oct 2014 14:01:17 +0800	[thread overview]
Message-ID: <1414044079-10006-1-git-send-email-helin.zhang@intel.com> (raw)

For those registers for early hardware only, they should neither
be defined nor be used. According to this, a header file which
defines all those registers should be deleted at all, and code
lines of accessing those registers should be deleted as well.

Helin Zhang (2):
  i40e: remove registers for early hardware only
  i40e: code style fix

 lib/librte_pmd_i40e/i40e/i40e_register_x710_int.h | 10712 --------------------
 lib/librte_pmd_i40e/i40e_ethdev.c                 |    25 +-
 2 files changed, 11 insertions(+), 10726 deletions(-)
 delete mode 100644 lib/librte_pmd_i40e/i40e/i40e_register_x710_int.h

-- 
1.8.1.4

             reply	other threads:[~2014-10-23  5:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-23  6:01 Helin Zhang [this message]
2014-10-23  6:01 ` [dpdk-dev] [PATCH 1/2] i40e: " Helin Zhang
2014-10-23  6:01 ` [dpdk-dev] [PATCH 2/2] i40e: code style fix Helin Zhang
2014-10-23  7:21 ` [dpdk-dev] [PATCH 0/2] remove registers for early hardware only Thomas Monjalon
2014-10-23  7:24   ` Thomas Monjalon
2014-10-23  7:27     ` Zhang, Helin
2014-10-23  7:31       ` Thomas Monjalon
2014-10-29  7:09 ` [dpdk-dev] [PATCH v2 " Helin Zhang
2014-10-29  7:09   ` [dpdk-dev] [PATCH v2 1/2] i40e: do not use macros defined in i40e_register_x710_int.h Helin Zhang
2014-10-29  7:09   ` [dpdk-dev] [PATCH v2 2/2] i40e: remove i40e_register_x710_int.h Helin Zhang
2014-10-29  8:53   ` [dpdk-dev] [PATCH v2 0/2] remove registers for early hardware only Wu, Jingjing
2014-10-29 22:59     ` 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=1414044079-10006-1-git-send-email-helin.zhang@intel.com \
    --to=helin.zhang@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).