test suite reviews and discussions
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "dev@dpdk.org" <dev@dpdk.org>, "dts@dpdk.org" <dts@dpdk.org>
Cc: nd <nd@arm.com>, "Lijuan Tu" <lijuan.tu@intel.com>,
	"Owen Hilyard" <ohilyard@iol.unh.edu>,
	"Lincoln Lavoie" <lylavoie@iol.unh.edu>,
	"Juraj Linkeš" <juraj.linkes@pantheon.tech>, nd <nd@arm.com>
Subject: DTS WG meeting minutes - 1/5/22
Date: Sat, 8 Jan 2022 01:30:56 +0000	[thread overview]
Message-ID: <DBAPR08MB58143EC75F16121C3E7C28D5984E9@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)

Hello,
	The first meeting in the new year for the DTS WG happened on 5th Jan. Going forward the meeting minutes will be captured in [1] to make it easy to keep track of the history.

Thanks,
Honnappa

[1] https://docs.google.com/document/d/1E2mkTHNQ5vyln1JvnJTil15cjacUTXP7LXb9K960Vxs/edit?usp=sharing

Attendees:
--------------
Honnappa Nagarahalli
Lincoln Lavoie
Owen Hilyard
Lijuan Tu

Agenda:
----------
1) Review pending action items
2) Understand where we are in fixing the issues currently
3) Changing the focus to creating the patches to DPDK repo

Minutes:
-----------
1) Juraj will join back the meetings in the week of January 17th
2) Juraj has sent patches to the community fixing Pylama tool reported issues. Lijuan mentioned that they are resulting in issues.
3) Owen has created the DTS contribution guidelines document. It is open for review for DTS WG for this week. It will be sent to the DTS and DPDK community for review tentatively on Jan 13th. https://docs.google.com/document/d/1G7_AEA-4MAd88bxjfP-IOcIy_6mnrMz3HCsUI8e-NN4/edit
4) The focus for the immediate future is to send the DTS framework patches to the DPDK community. This will help further prioritize the work items from the 'MUST HAVE' list.

Action Items:
-----------------
1) Lijuan - Many test cases in DTS modify the DPDK code to change the max/min values of constants. List all the constants and send it to Honnappa to address in DPDK code.
2) Lijuan - Review the DTS DPDK modifications document and classify the work items into 'Closed' (does not need further actions), 'In progress' (someone is working on it) and 'Open' (need to understand the issue)
3) All - Review Owen's DTS contributions guide
4) Owen - Send the DTS contribution guide for review to DPDK and DTS community after next week's call

Any other business:
--------------------------
Next Meeting: January 12, 2022

                 reply	other threads:[~2022-01-08  1:31 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=DBAPR08MB58143EC75F16121C3E7C28D5984E9@DBAPR08MB5814.eurprd08.prod.outlook.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=dev@dpdk.org \
    --cc=dts@dpdk.org \
    --cc=juraj.linkes@pantheon.tech \
    --cc=lijuan.tu@intel.com \
    --cc=lylavoie@iol.unh.edu \
    --cc=nd@arm.com \
    --cc=ohilyard@iol.unh.edu \
    /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).