From: Pallavi Kadam <pallavi.kadam@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, anand.rawat@intel.com
Subject: Re: [dpdk-dev] [PATCH] doc: update release notes for windows support
Date: Tue, 23 Apr 2019 09:18:37 -0700 [thread overview]
Message-ID: <a9423093-b681-2de5-9380-04a5eaa32ffb@intel.com> (raw)
Message-ID: <20190423161837.GHcoHn5XdhysRuWBNHpVpx6LZSXhFJBv7DEo8KXpGlw@z> (raw)
In-Reply-To: <2405978.gfNxMDCiSY@xps>
On 4/22/2019 3:42 PM, Thomas Monjalon wrote:
> 10/04/2019 23:00, Pallavi Kadam:
>> Added documentation for Windows support on 19.05 release.
>>
>> Signed-off-by: Pallavi Kadam <pallavi.kadam@intel.com>
>> Reviewed-by: Anand Rawat <anand.rawat@intel.com>
>> ---
>> +* **Added Windows Support.**
>> +
>> + * Added Windows support to compile and build Hello World Sample Application.
>> + * Added Windows-specific EAL changes and meson changes.
>> + * Added windows support for kvargs.
> You forgot the uppercase for Windows.
>
>> + * Updated meson for building DLL on windows using DEF files.
>> + * Added rte_os.h for essential os specific macros and typedefs
>> + * Updated make build system to include path for rte_os.h.
> I think this is too much details for a release notes.
> The useful information here is the first item explaining the
> support level is for compiling helloworld.
Ok, will reduce it in v2.
next prev parent reply other threads:[~2019-04-23 16:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 21:00 Pallavi Kadam
2019-04-10 21:00 ` Pallavi Kadam
2019-04-22 22:42 ` Thomas Monjalon
2019-04-22 22:42 ` Thomas Monjalon
2019-04-23 16:18 ` Pallavi Kadam [this message]
2019-04-23 16:18 ` Pallavi Kadam
2019-04-23 18:12 ` [dpdk-dev] [PATCH v2] " Pallavi Kadam
2019-04-23 18:12 ` Pallavi Kadam
2019-05-02 15:57 ` Mcnamara, John
2019-05-02 15:57 ` Mcnamara, John
2019-05-04 21:56 ` Thomas Monjalon
2019-05-04 21:56 ` 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=a9423093-b681-2de5-9380-04a5eaa32ffb@intel.com \
--to=pallavi.kadam@intel.com \
--cc=anand.rawat@intel.com \
--cc=dev@dpdk.org \
--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).