test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Wang, Yinan" <yinan.wang@intel.com>
To: "Ma, LihongX" <lihongx.ma@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1 2/2][vhost peer conf] tests: add common method file to read conf file
Date: Wed, 17 Jul 2019 06:18:01 +0000	[thread overview]
Message-ID: <E0CBA5A1980F1F408E1F28F9991B5B1D50EC5A02@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1563313688-4457-2-git-send-email-lihongx.ma@intel.com>

Acked-by: Wang, Yinan <yinan.wang@intel.com>

> -----Original Message-----
> From: Ma, LihongX
> Sent: 2019年7月17日 5:48
> To: dts@dpdk.org
> Cc: Wang, Yinan <yinan.wang@intel.com>; Ma, LihongX <lihongx.ma@intel.com>
> Subject: [dts][PATCH V1 2/2][vhost peer conf] tests: add common method file to
> read conf file
> 
> Signed-off-by: lihong <lihongx.ma@intel.com>
> ---
>  tests/vhost_peer_conf.py | 48
> ++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 48 insertions(+)
>  create mode 100644 tests/vhost_peer_conf.py
> 
> diff --git a/tests/vhost_peer_conf.py b/tests/vhost_peer_conf.py new file mode
> 100644 index 0000000..59b3495
> --- /dev/null
> +++ b/tests/vhost_peer_conf.py
> @@ -0,0 +1,48 @@
> +# BSD LICENSE
> +#
> +# Copyright(c) <2019> Intel Corporation.
> +# All rights reserved.
> +#
> +# Redistribution and use in source and binary forms, with or without #
> +modification, are permitted provided that the following conditions #
> +are met:
> +#
> +#   * Redistributions of source code must retain the above copyright
> +#     notice, this list of conditions and the following disclaimer.
> +#   * Redistributions in binary form must reproduce the above copyright
> +#     notice, this list of conditions and the following disclaimer in
> +#     the documentation and/or other materials provided with the
> +#     distribution.
> +#   * Neither the name of Intel Corporation nor the names of its
> +#     contributors may be used to endorse or promote products derived
> +#     from this software without specific prior written permission.
> +#
> +# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
> CONTRIBUTORS #
> +"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT #
> +LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
> #
> +A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
> #
> +OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
> #
> +SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT #
> +LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
> #
> +DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
> ANY #
> +THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT #
> +(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
> USE #
> +OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
> +
> +from config import UserConf
> +
> +conf_file = 'conf/vhost_peer_conf.cfg'
> +conf_peer = UserConf(conf_file)
> +conf_session = conf_peer.conf._sections['peerconf']
> +
> +def get_pci_info():
> +    return conf_session['pci']
> +
> +def get_pci_peer_info():
> +    return conf_session['peer']
> +
> +def get_pci_driver_info():
> +    return conf_session['pci_drv']
> +
> +def get_pci_peer_intf_info():
> +    return conf_session['peer_intf']
> --
> 2.7.4


  reply	other threads:[~2019-07-17  6:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-16 21:48 [dts] [PATCH V1 1/2][vhost peer conf] conf: add cfg file of vhost peer direct connection lihong
2019-07-16 21:48 ` [dts] [PATCH V1 2/2][vhost peer conf] tests: add common method file to read conf file lihong
2019-07-17  6:18   ` Wang, Yinan [this message]
2019-07-17  6:21     ` Ma, LihongX
2019-08-07  3:46   ` Tu, Lijuan
2019-07-17  6:18 ` [dts] [PATCH V1 1/2][vhost peer conf] conf: add cfg file of vhost peer direct connection Wang, Yinan
2019-07-17  6:22   ` Ma, LihongX
2019-08-07  3:46 ` 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=E0CBA5A1980F1F408E1F28F9991B5B1D50EC5A02@SHSMSX104.ccr.corp.intel.com \
    --to=yinan.wang@intel.com \
    --cc=dts@dpdk.org \
    --cc=lihongx.ma@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).