From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: Robin Jarry <rjarry@redhat.com>, <dev@dpdk.org>
Cc: Olivier Matz <olivier.matz@6wind.com>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v4] usertools: rewrite pmdinfo
Date: Wed, 21 Sep 2022 10:57:36 +0100 [thread overview]
Message-ID: <6fe7e052-0ff3-e228-9348-2cc7ed2e47c1@xilinx.com> (raw)
In-Reply-To: <d3deb7a6-3332-8f2d-10d7-f6881eccf9ec@xilinx.com>
On 9/21/2022 8:58 AM, Ferruh Yigit wrote:
> On 9/20/2022 8:15 PM, Robin Jarry wrote:
>
>>
>> Ferruh Yigit, Sep 20, 2022 at 19:48:
>>>> +* The ``dpdk-pmdinfo.py`` script was rewritten to produce valid
>>>> JSON only.
>>>> + PCI-IDs parsing has been removed.
>>>> + To get a similar output to the (now removed) ``-r/--raw`` flag,
>>>> you may use the following command::
>>>> +
>>>> + strings $dpdk_binary_or_driver | sed -n 's/^PMD_INFO_STRING= //p'
>>>>
>>>
>>> Empty line is missing (in case there will be a new version for some
>>> other reason).
>>
>> What do you mean?
>>
>
> just nit picking, there needs to be two empty lines before "ABI
> Changes", I assume committer can fix it while merging if there won't be
> any new version.
Also looking twice, this release note update is in "API Changes"
section, I think that is not correct place, "New Features" section can
be better place.
next prev parent reply other threads:[~2022-09-21 9:57 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 10:58 [PATCH] " Robin Jarry
2022-09-13 11:29 ` Ferruh Yigit
2022-09-13 11:49 ` Robin Jarry
2022-09-13 13:50 ` Ferruh Yigit
2022-09-13 13:59 ` Robin Jarry
2022-09-13 14:17 ` Ferruh Yigit
2022-09-13 14:17 ` Bruce Richardson
2022-09-13 19:42 ` [PATCH v2] " Robin Jarry
2022-09-13 20:54 ` Ferruh Yigit
2022-09-13 21:22 ` Robin Jarry
2022-09-14 11:46 ` Ferruh Yigit
2022-09-15 9:18 ` Robin Jarry
2022-09-20 9:08 ` [PATCH v3] " Robin Jarry
2022-09-20 10:10 ` Ferruh Yigit
2022-09-20 10:12 ` Robin Jarry
2022-09-20 10:42 ` [PATCH v4] " Robin Jarry
2022-09-20 14:08 ` Olivier Matz
2022-09-20 17:48 ` Ferruh Yigit
2022-09-20 17:50 ` Ferruh Yigit
2022-09-21 7:27 ` Thomas Monjalon
2022-09-21 8:02 ` Ferruh Yigit
2022-09-20 19:15 ` Robin Jarry
2022-09-21 7:58 ` Ferruh Yigit
2022-09-21 9:57 ` Ferruh Yigit [this message]
2022-09-22 11:58 ` [PATCH v5] " Robin Jarry
2022-09-22 12:03 ` Bruce Richardson
2022-09-22 15:12 ` Ferruh Yigit
2022-09-26 11:55 ` Olivier Matz
2022-09-26 12:52 ` Robin Jarry
2022-09-26 13:44 ` [PATCH v6] " Robin Jarry
2022-09-26 15:17 ` Bruce Richardson
2022-09-28 6:51 ` Robin Jarry
2022-09-28 10:53 ` Bruce Richardson
2022-09-28 11:12 ` Robin Jarry
2022-10-04 19:29 ` [PATCH v7] " Robin Jarry
2022-10-10 22:44 ` Thomas Monjalon
2022-10-12 15:16 ` Olivier Matz
2022-10-12 16:16 ` Thomas Monjalon
2022-10-12 16:30 ` Robin Jarry
2022-10-12 16:44 ` Thomas Monjalon
2022-10-12 16:48 ` Robin Jarry
2022-10-12 20:40 ` 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=6fe7e052-0ff3-e228-9348-2cc7ed2e47c1@xilinx.com \
--to=ferruh.yigit@xilinx.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=rjarry@redhat.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).