DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v1] doc: update release notes for 21.02
Date: Fri, 12 Feb 2021 11:14:27 +0300	[thread overview]
Message-ID: <20210212111427.2d93cf26@sovereign> (raw)
In-Reply-To: <2223013.YjMRiKvppQ@thomas>

On Fri, 12 Feb 2021 00:33:35 +0100, Thomas Monjalon wrote:
> 11/02/2021 13:08, Mcnamara, John:
> > Also, there probably should be a note about the change to pmdinfogen
> > in this release. I didn't know enough about it to add it myself.  
> 
> Yes it is a rewrite of a build tool.
> The real new feature is the support of Windows for pmdinfo.
> 
> +Cc Dmitry for helping with the wording.

* **Added Windows support to pmdinfogen.**

  PMD information strings are added for Windows as well as for other OS.
  Extracting them from Windows DLLs is not yet supported. A build-time tool
  pmdinfogen is rewritten in Python, thus native compiler and libelf are not
  required for build machine anymore, but pyelftools build-time dependency is
  added.

Feel free to use and/or adjust.

  reply	other threads:[~2021-02-12  8:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 12:04 John McNamara
2021-02-11 12:08 ` Mcnamara, John
2021-02-11 23:33   ` Thomas Monjalon
2021-02-12  8:14     ` Dmitry Kozlyuk [this message]
2021-02-12 11:57     ` Bruce Richardson
2021-02-12 12:49       ` Thomas Monjalon
2021-02-12 13:30         ` Bruce Richardson
2021-02-12 13:52           ` Thomas Monjalon
2021-02-14  9:57 ` 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=20210212111427.2d93cf26@sovereign \
    --to=dmitry.kozliuk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=thomas@monjalon.net \
    /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).