From: Tal Shnaiderman <talshn@nvidia.com>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>,
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
Pallavi Kadam <pallavi.kadam@intel.com>,
Khoa To <khot@microsoft.com>
Subject: Re: [dpdk-dev] [PATCH] metrics/windows: build rte_metrics library
Date: Tue, 12 Jan 2021 06:44:23 +0000 [thread overview]
Message-ID: <DM6PR12MB3945D75332AC57AE0B5C8A2BA4AA0@DM6PR12MB3945.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210112013238.GA10665@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
> Subject: Re: [dpdk-dev] [PATCH] metrics/windows: build rte_metrics library
>
> On Tue, Jan 12, 2021 at 04:15:34AM +0300, Dmitry Kozlyuk wrote:
> > + Pallavi, Khoa
> >
> > What's the future plan? Once we talked about a script that would
> > inspect objects and filter missing functions from the list in .map to
> > build .def. Is MSFT working on it? Or do we choose another way?
>
> MSFT has a task tracking work to resolve this. We agree it is cumbersome to
> try and keep the .map and .def files in sync by hand.
Is there a DD to complete this task? Dmitry already sent an email with the details on how to resolve it using DUMPBIN.
next prev parent reply other threads:[~2021-01-12 6:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 23:37 Tyler Retzlaff
2021-01-12 1:15 ` Dmitry Kozlyuk
2021-01-12 1:32 ` Tyler Retzlaff
2021-01-12 6:44 ` Tal Shnaiderman [this message]
2021-01-12 1:30 ` [dpdk-dev] [PATCH v2] " Tyler Retzlaff
2021-01-17 22:19 ` Thomas Monjalon
2021-01-19 21:31 ` Tyler Retzlaff
2021-01-19 21:52 ` Thomas Monjalon
2021-01-20 10:37 ` Bruce Richardson
2021-01-20 11:09 ` Thomas Monjalon
2021-01-20 11:54 ` Bruce Richardson
2021-01-20 12:13 ` Thomas Monjalon
2021-01-20 13:57 ` Bruce Richardson
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=DM6PR12MB3945D75332AC57AE0B5C8A2BA4AA0@DM6PR12MB3945.namprd12.prod.outlook.com \
--to=talshn@nvidia.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=khot@microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=roretzla@linux.microsoft.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).