From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
dev@dpdk.org, dmitry.kozliuk@gmail.com
Subject: Re: [dpdk-dev] [PATCH v1] doc: update release notes for 21.02
Date: Fri, 12 Feb 2021 11:57:38 +0000 [thread overview]
Message-ID: <20210212115738.GA970@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <2223013.YjMRiKvppQ@thomas>
On Fri, Feb 12, 2021 at 12:33:35AM +0100, Thomas Monjalon wrote:
> 11/02/2021 13:08, Mcnamara, John:
>
> > Thomas,
> >
> > I didn't remove the "Known Issues" section in case someone else
> > adds something to it. If not you can remove it.
>
> OK, I will remove.
>
Should the new dependency on pyelftools be called out here? Since it's not
a common package I think it needs to be emphasised as a new dependency and
instructions on how to get it.
> > 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.
>
>
next prev parent reply other threads:[~2021-02-12 11:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 12:04 [dpdk-dev] [PATCH v1] doc: update release notes for 21.02 John McNamara
2021-02-11 12:08 ` Mcnamara, John
2021-02-11 23:33 ` Thomas Monjalon
2021-02-12 8:14 ` Dmitry Kozlyuk
2021-02-12 11:57 ` Bruce Richardson [this message]
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=20210212115738.GA970@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.