DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Helin" <helin.zhang@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/2] remove registers for early hardware only
Date: Thu, 23 Oct 2014 07:27:06 +0000	[thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A7AA6D5@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <6734152.2yIzpFtZi3@xps13>

Hi Thomas

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Thursday, October 23, 2014 3:25 PM
> To: Zhang, Helin
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH 0/2] remove registers for early hardware only
> 
> > The first patch is missing.
> 
> It was blocked in moderation queue because of its size.
Yes, the first patch includes removing a head file of about 10,000 lines of code.
I need to do nothing, right?

> 
> --
> Thomas

Thanks,
Helin

  reply	other threads:[~2014-10-23  7:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-23  6:01 Helin Zhang
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 [this message]
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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A7AA6D5@SHSMSX104.ccr.corp.intel.com \
    --to=helin.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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).