From: "Dong, JunX" <junx.dong@intel.com>
To: "Juraj Linkeš" <juraj.linkes@pantheon.tech>,
"Tu, Lijuan" <lijuan.tu@intel.com>,
"ohilyard@iol.unh.edu" <ohilyard@iol.unh.edu>
Cc: "dts@dpdk.org" <dts@dpdk.org>
Subject: RE: [PATCH v2] framework/dut: fix pylama errors
Date: Tue, 25 Jan 2022 03:30:44 +0000 [thread overview]
Message-ID: <BN9PR11MB52744B1D824D14F440173735EA5F9@BN9PR11MB5274.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1642593951-10980-1-git-send-email-juraj.linkes@pantheon.tech>
> -----Original Message-----
> From: Juraj Linkeš <juraj.linkes@pantheon.tech>
> Sent: Wednesday, January 19, 2022 8:06 PM
> To: Tu, Lijuan <lijuan.tu@intel.com>; ohilyard@iol.unh.edu; Dong, JunX
> <junx.dong@intel.com>
> Cc: dts@dpdk.org; Juraj Linkeš <juraj.linkes@pantheon.tech>
> Subject: [PATCH v2] framework/dut: fix pylama errors
>
> Pylama found the following errors:
> framework/dut.py:273: [E] E0602 Undefined variable 'threading' [pylint]
> framework/dut.py:591: [E] E1101 Instance of 'Dut' has no
> 'get_def_rte_config' member [pylint]
> - move the method from child class
> framework/dut.py:631: [E] E0602 Undefined variable 'crbs' [pylint]
> framework/dut.py:840: [E] E0602 Undefined variable 'ResultTable' [pylint]
> framework/dut.py:846: [E] E0602 Undefined variable 'ResultTable' [pylint]
> framework/dut.py:929: [E] E0602 Undefined variable 'pci_bus' [pylint]
> framework/dut.py:1173: [E] E0602 Undefined variable 'VMCORELIST' [pylint]
> - remove unused method
>
> Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
> ---
> Lijuan, please add additional people to review if needed.
> ---
Tested-by: Jun Dong <junx. dong@intel.com>
next prev parent reply other threads:[~2022-01-25 3:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 12:14 [PATCH v1] " Juraj Linkeš
2021-12-06 13:55 ` David Marchand
2022-01-18 13:59 ` Juraj Linkeš
2022-01-07 7:42 ` Dong, JunX
2022-01-19 12:05 ` [PATCH v2] " Juraj Linkeš
2022-01-25 3:30 ` Dong, JunX [this message]
2022-01-25 6:02 ` 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=BN9PR11MB52744B1D824D14F440173735EA5F9@BN9PR11MB5274.namprd11.prod.outlook.com \
--to=junx.dong@intel.com \
--cc=dts@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--cc=lijuan.tu@intel.com \
--cc=ohilyard@iol.unh.edu \
/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).