From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Xu, Qian Q" <qian.q.xu@intel.com>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v1] doc:add tested platforms and nics
Date: Fri, 08 Apr 2016 16:47:40 +0200 [thread overview]
Message-ID: <2126301.mhDi6LQXts@xps13> (raw)
In-Reply-To: <82F45D86ADE5454A95A89742C8D1410E03236545@shsmsx102.ccr.corp.intel.com>
2016-04-08 14:29, Xu, Qian Q:
> Agreed, and others can add their NICs info into the tested NICs and platforms. One question about the release version, the NICs and platforms may change with the release version, for example, for each release, the information may be different, so we need mention the release version for the tested nics and platforms. Then how about putting them in one session of release notes?
Please do at your convenience but do it quickly.
Thanks
> -----Original Message-----
> From: Mcnamara, John
> Sent: Friday, April 08, 2016 6:05 PM
> To: Thomas Monjalon; Xu, Qian Q
> Cc: dev@dpdk.org
> Subject: RE: [dpdk-dev] [PATCH v1] doc:add tested platforms and nics
>
> > -----Original Message-----
> > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > Sent: Friday, April 8, 2016 10:06 AM
> > To: Xu, Qian Q <qian.q.xu@intel.com>
> > Cc: dev@dpdk.org; Mcnamara, John <john.mcnamara@intel.com>
> > Subject: Re: [dpdk-dev] [PATCH v1] doc:add tested platforms and nics
> >
> > > overview
> > > + test_platforms
> >
> > I think it would be better suited to integrate this information in the
> > existing pages for e1000, ixgbe, i40e and fm10k.
>
> Hi,
>
> I think that this is better in one section where it can be reviewed together. I think it should be the last chapter in the section though.
>
> John.
>
next prev parent reply other threads:[~2016-04-08 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 8:57 Qian Xu
2016-04-08 9:05 ` Thomas Monjalon
2016-04-08 10:04 ` Mcnamara, John
2016-04-08 14:29 ` Xu, Qian Q
2016-04-08 14:47 ` Thomas Monjalon [this message]
2016-04-08 10:02 ` Mcnamara, John
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=2126301.mhDi6LQXts@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=qian.q.xu@intel.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).