From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "'ci@dpdk.org'" <ci@dpdk.org>
Cc: 'Bob Noseworthy' <ren@iol.unh.edu>,
"Mcnamara, John" <john.mcnamara@intel.com>,
'Shepard Siegel' <shepard.siegel@atomicrules.com>,
'Thomas Monjalon' <thomas@monjalon.net>,
'Erez Scop' <erezsc@mellanox.com>,
'Shreyansh Jain' <shreyansh.jain@nxp.com>,
"Xu, Qian Q" <qian.q.xu@intel.com>,
"'pmacarth@iol.unh.edu'" <pmacarth@iol.unh.edu>,
"'Matt Spencer'" <Matt.Spencer@arm.com>,
Gema Gomez <gema.gomez-solano@linaro.org>,
'George Zhao' <George.Y.Zhao@huawei.com>,
"Mishra, Shishir" <Shishir.Mishra@spirent.com>,
'Lixuming' <lixuming@huawei.com>,
"Tkachuk, Georgii" <georgii.tkachuk@intel.com>,
'Trishan de Lanerolle' <tdelanerolle@linuxfoundation.org>,
Sean Campbell <scampbel@qti.qualcomm.com>
Subject: [dpdk-ci] Minutes of DPDK Lab Meeting, December 12th
Date: Tue, 12 Dec 2017 14:51:37 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAA4A89D54@IRSMSX108.ger.corp.intel.com> (raw)
Attendance was limited so this was a short call. Here are some brief minutes.
Database Schema:
- Patrick has updated the schema based on the discussion we had at the last meeting. See http://dpdk.org/ml/archives/ci/2017-November/000150.html. If anybody has further comments on this, please let Patrick know.
DTS & TRex:
- I'll check on status/plans for this with Qian and her team.
Hardware availability:
- Intel equipment is almost ready for shipping to UNH.
- NXP are targeting end of Jan for shipping to UNH.
Misc:
- Patrick would like sample output from test cases. I'll ask our validation team to provide this.
- UNH have been working on infrastructure so that they're ready when hardware arrives.
Next Meeting:
- Tuesday Jan 9th.
reply other threads:[~2017-12-12 14:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=26FA93C7ED1EAA44AB77D62FBE1D27BAA4A89D54@IRSMSX108.ger.corp.intel.com \
--to=tim.odriscoll@intel.com \
--cc=George.Y.Zhao@huawei.com \
--cc=Matt.Spencer@arm.com \
--cc=Shishir.Mishra@spirent.com \
--cc=ci@dpdk.org \
--cc=erezsc@mellanox.com \
--cc=gema.gomez-solano@linaro.org \
--cc=georgii.tkachuk@intel.com \
--cc=john.mcnamara@intel.com \
--cc=lixuming@huawei.com \
--cc=pmacarth@iol.unh.edu \
--cc=qian.q.xu@intel.com \
--cc=ren@iol.unh.edu \
--cc=scampbel@qti.qualcomm.com \
--cc=shepard.siegel@atomicrules.com \
--cc=shreyansh.jain@nxp.com \
--cc=tdelanerolle@linuxfoundation.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).