From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Christos Ricudis <ricudis@niometrics.com>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] usertools: decode PCI device name as UTF-8
Date: Mon, 13 Apr 2020 18:14:06 +0300 [thread overview]
Message-ID: <fd45413a-4272-8a97-a48a-099690ff33c1@solarflare.com> (raw)
In-Reply-To: <1586789914-10825-1-git-send-email-ricudis@niometrics.com>
On 4/13/20 5:58 PM, Christos Ricudis wrote:
> Fixes the case where a PCI device string identifier contains non-ASCII UTF-8.
>
> A particular example is Mellanox Connext-X 5 EN MT27800:
>
> 28:00.0 Ethernet controller: Mellanox Technologies MT27800 Family [ConnectX-5]
> Subsystem: Mellanox Technologies ConnectX®-5 EN network interface card, 100GbE single-port QSFP28, PCIe3.0 x16, tall bracket; MCX515A-CCAT
>
> Signed-off-by: Christos Ricudis <ricudis@niometrics.com>
> ---
> usertools/dpdk-devbind.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/usertools/dpdk-devbind.py b/usertools/dpdk-devbind.py
> index b1d1498..8ec1703 100755
> --- a/usertools/dpdk-devbind.py
> +++ b/usertools/dpdk-devbind.py
> @@ -257,7 +257,7 @@ def get_device_details(devices_type):
> # Clear previous device's data
> dev = {}
> else:
> - name, value = dev_line.decode().split("\t", 1)
> + name, value = dev_line.decode("utf8").split("\t", 1)
> value_list = value.rsplit(' ', 1)
> if len(value_list) > 1:
> # String stored in <name>_str
>
Is similar fix required in line 214 as well?
name, value = line.decode('utf-8').split("\t", 1)
next prev parent reply other threads:[~2020-04-13 15:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 14:58 Christos Ricudis
2020-04-13 15:14 ` Andrew Rybchenko [this message]
2020-04-13 15:36 ` Christos Rikoudis
2020-04-13 16:18 ` [dpdk-dev] [PATCH v2] " Christos Ricudis
2020-04-13 16:19 ` Andrew Rybchenko
2020-05-24 17:10 ` 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=fd45413a-4272-8a97-a48a-099690ff33c1@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ricudis@niometrics.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).