From: "Liu, Yong" <yong.liu@intel.com>
To: "Fan, ChangruX" <changrux.fan@intel.com>
Cc: "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] Debug vlan and dual_vlan failed cases
Date: Mon, 20 Jul 2015 04:24:01 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E10E65002@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <84799DAADE9E2A44834F0D0FF8A61A914BEE76@SHSMSX101.ccr.corp.intel.com>
Hi Changru,
Can you send your patch just with plain txt? And please fix the pep8 issue in the suite, now I have to reform your patch.
From: Fan, ChangruX
Sent: Monday, July 20, 2015 10:31 AM
To: Liu, Yong; dts@dpdk.org
Subject: FW: Debug vlan and dual_vlan failed cases
Hi Yong
Attach files are the patch for vlan and dual_vlan.
Thanks
changru
From: Fan, ChangruX
Sent: Thursday, July 16, 2015 3:56 PM
To: Xu, HuilongX
Cc: Chen, WeichunX
Subject: RE: Debug vlan and dual_vlan failed cases
Hi huilong,
I have removed the annotation. Please check.
Thanks
From: Xu, HuilongX
Sent: Thursday, July 16, 2015 10:33 AM
To: Fan, ChangruX; Xu, HuilongX
Cc: Chen, WeichunX
Subject: RE: Debug vlan and dual_vlan failed cases
Hi changru,
I check your patch already, could you remove the annotation in your patch, because some annotation is debug info.
Thanks a lot
From: Fan, ChangruX
Sent: Wednesday, July 15, 2015 6:57 PM
To: Xu, HuilongX; dts@dpdk.org
Subject: Debug vlan and dual_vlan failed cases
Hi huilong
After apply the patch, the vlan and dual_vlan can passed testing.
changru
prev parent reply other threads:[~2015-07-20 4:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <84799DAADE9E2A44834F0D0FF8A61A914BE7D6@SHSMSX101.ccr.corp.intel.com>
[not found] ` <DF2A19295B96364286FEB7F3DDA27A460112DF81@SHSMSX101.ccr.corp.intel.com>
[not found] ` <84799DAADE9E2A44834F0D0FF8A61A914BE9E4@SHSMSX101.ccr.corp.intel.com>
2015-07-20 2:31 ` [dts] FW: " Fan, ChangruX
2015-07-20 4:24 ` Liu, Yong [this message]
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=86228AFD5BCD8E4EBFD2B90117B5E81E10E65002@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=changrux.fan@intel.com \
--cc=dts@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).