test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Xu, HailinX" <hailinx.xu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Xu, HailinX" <hailinx.xu@intel.com>
Subject: Re: [dts] [PATCH v1]test_plans/iavf: modify the sed command according	to dpdk code
Date: Fri, 20 Mar 2020 08:07:27 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BBEFAB6@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1584425618-144062-1-git-send-email-hailinx.xu@intel.com>

Applied failed, please rework

Applying: test_plans/iavf: modify the sed command according to dpdk code
error: patch failed: test_plans/iavf_test_plan.rst:45
error: test_plans/iavf_test_plan.rst: patch does not apply
Patch failed at 0001 test_plans/iavf: modify the sed command according to dpdk code

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of xuhailin
> Sent: Tuesday, March 17, 2020 2:14 PM
> To: dts@dpdk.org
> Cc: Xu, HailinX <hailinx.xu@intel.com>
> Subject: [dts] [PATCH v1]test_plans/iavf: modify the sed command according
> to dpdk code
> 
> From: "xu,hailin" <hailinx.xu@intel.com>
> 
> modify the sed command according to dpdk code.
> 
> Signed-off-by: xu,hailin <hailinx.xu@intel.com>
> ---
>  test_plans/iavf_test_plan.rst | 6 ++----
>  1 file changed, 2 insertions(+), 4 deletions(-)
> 
> diff --git a/test_plans/iavf_test_plan.rst b/test_plans/iavf_test_plan.rst index
> 2a21546..cbbcaa5 100644
> --- a/test_plans/iavf_test_plan.rst
> +++ b/test_plans/iavf_test_plan.rst
> @@ -45,8 +45,7 @@ Prerequisites
>  =======================
>  1. Modify and build DPDK source code to enable IAVF function for I40E NIC::
> 
> -    sed -i '/{ RTE_PCI_DEVICE(IAVF_INTEL_VENDOR_ID,
> IAVF_DEV_ID_ADAPTIVE_VF) }, \
> -    /a { RTE_PCI_DEVICE(IAVF_INTEL_VENDOR_ID, IAVF_DEV_ID_VF) },'
> drivers/net/iavf/iavf_ethdev.c
> +    sed -i '/{ RTE_PCI_DEVICE(IAVF_INTEL_VENDOR_ID,
> + IAVF_DEV_ID_ADAPTIVE_VF) },/a
> { RTE_PCI_DEVICE(IAVF_INTEL_VENDOR_ID,
> + IAVF_DEV_ID_VF) },' drivers/net/iavf/iavf_ethdev.c
>      sed -i -e '/I40E_DEV_ID_VF/s/0x154C/0x164C/g'
> drivers/net/i40e/base/i40e_devids.h
> 
>      make install RTE_SDK=`pwd` T=x86_64-native-linuxapp-gcc @@ -80,8
> +79,7 @@ Prerequisites
> 
>  5. Modify and build DPDK source code to enable IAVF function for I40E NIC
> in VM::
> 
> -    sed -i '/{ RTE_PCI_DEVICE(IAVF_INTEL_VENDOR_ID,
> IAVF_DEV_ID_ADAPTIVE_VF) }, \
> -    /a { RTE_PCI_DEVICE(IAVF_INTEL_VENDOR_ID, IAVF_DEV_ID_VF) },'
> drivers/net/iavf/iavf_ethdev.c
> +    sed -i '/{ RTE_PCI_DEVICE(IAVF_INTEL_VENDOR_ID,
> + IAVF_DEV_ID_ADAPTIVE_VF) },/a
> { RTE_PCI_DEVICE(IAVF_INTEL_VENDOR_ID,
> + IAVF_DEV_ID_VF) },' drivers/net/iavf/iavf_ethdev.c
>      sed -i -e '/I40E_DEV_ID_VF/s/0x154C/0x164C/g'
> drivers/net/i40e/base/i40e_devids.h
> 
>      make install RTE_SDK=`pwd` T=x86_64-native-linuxapp-gcc
> --
> 1.8.3.1


  parent reply	other threads:[~2020-03-20  8:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-17  6:13 xuhailin
2020-03-17  6:29 ` Xu, HailinX
2020-03-20  8:07 ` Tu, Lijuan [this message]
2020-03-23  3:17 [dts] [PATCH v1]test_plans/iavf:modify " xuhailin
2020-03-23  3:27 ` Xu, HailinX
2020-03-24  6:51 ` Tu, Lijuan

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=8CE3E05A3F976642AAB0F4675D0AD20E0BBEFAB6@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=hailinx.xu@intel.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).