DPDK CI discussions
 help / color / mirror / Atom feed
From: Owen Hilyard <ohilyard@iol.unh.edu>
To: ci@dpdk.org, dts@dpdk.org
Subject: DTS WG Minutes 2/09/22
Date: Wed, 9 Feb 2022 10:00:12 -0500	[thread overview]
Message-ID: <CAHx6DYA7+AHMLWBGjxjO1au1S6DdGgRc5GjQ+qfpPz0FtGYRGw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3463 bytes --]

Attendees

   -

   Owen Hilyard
   -

   Honnappa Nagarahalli
   -

   Lincoln Lavoie
   -

   Bruce Richardson
   -

   Lijuan Tu

Agenda

   -

   Additions to the agenda
   -

   Review/Carry forward pending action items
   -

   Disallowing parsing using regular expressions
   -

   Merging DTS into DPDK
   -

   Review additional work items

MinutesReview/Carry forward pending action items

   -

   Honnappa - Patches to DPDK to address changing the constants and printfs
   under progress.
   -

      No change
      -

   Honnappa - The changes to DPDK need to be backported to LTS releases.
   Discuss with Lijuan and the community.
   -

      Backporting the changes to LTS releases is the preferred option. This
      will allow single DTS to be used with all the releases.
      -

      Discuss with the community if it is ok to merge these patches with
      the LTS release.
      -

   All - Review Owen’s DTS contributions guide, Owen to review Juraj’s
   feedback.
   -

      Closing Feedback
      -

   Lijuan - Create release notes, capture the makefile deprecation.
   -

      Will send out later today
      -

   Honnappa - Follow up with DPDK governing board to get the approval/legal
   opinion on including the GPL licensed files from DTS in the DPDK tree.
   -

      No change
      -

   Owen - Look at making DTS build using the common DPDK repo in addition
   to the existing tarball option.
   -

      No change
      -

      $ meson dist
      -

   Lijuan - The makefile removal patch is ready to get merged (
   http://patchwork.dpdk.org/project/dts/list/?series=20610). Merge it in
   the 22.03 DTS release.
   -

      Not present / No Change
      -

   Juraj - Postponed: Convert the makefile build for documentation to use
   meson build after merging the repositories or the directory structure is
   known.
   -

      Not present

Merging DTS into DPDK

   -

   Are we going to integrate DTS with the DPDK build system? No resolution
   yet.
   -

   Try for 22.07
   -

   Focus on framework and test cases used in CI
   -

   Do a deep dive on Feb 9th - identify what needs to be done and estimate
   the work.

Action Items

   -

   Honnappa - Patches to DPDK to address changing the constants and printfs
   under progress.
   -

   Honnappa - The changes to DPDK need to be backported to LTS releases.
   Discuss with Lijuan and the community.
   -

   Owen - Owen to review Juraj’s feedback.
   -

   Lijuan - Create release notes, capture the makefile deprecation.
   -

   Honnappa - Follow up with DPDK governing board to get the approval/legal
   opinion on including the GPL licensed files from DTS in the DPDK tree.
   -

   Owen - Look at making DTS build using the common DPDK repo in addition
   to the existing tarball option.
   -

   Lijuan - The makefile removal patch is ready to get merged (
   http://patchwork.dpdk.org/project/dts/list/?series=20610). Merge it in
   the 22.03 DTS release.
   -

   Juraj - Postponed: Convert the makefile build for documentation to use
   meson build after merging the repositories or the directory structure is
   known.
   -

   Honnappa - Discuss merge permissions for Owen for the DTS tree with the
   Tech Board

Any other business

   -

   Next Meeting: February 16, 2022

[-- Attachment #2: Type: text/html, Size: 27095 bytes --]

                 reply	other threads:[~2022-02-09 15:00 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=CAHx6DYA7+AHMLWBGjxjO1au1S6DdGgRc5GjQ+qfpPz0FtGYRGw@mail.gmail.com \
    --to=ohilyard@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=dts@dpdk.org \
    /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).