From: Owen Hilyard <ohilyard@iol.unh.edu>
To: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Cc: "dts@dpdk.org" <dts@dpdk.org>,
"lijuan.tu@intel.com" <lijuan.tu@intel.com>
Subject: Re: [PATCH] Fix hardcoded config folders
Date: Tue, 18 Jan 2022 10:21:31 -0500 [thread overview]
Message-ID: <CAHx6DYDv6pN7R+8nVVu5H9xtabfxMQ0_ZoHEEZ=-hCgUzr=k2w@mail.gmail.com> (raw)
In-Reply-To: <f92a1d93009c48afa624713aeda152bd@pantheon.tech>
[-- Attachment #1: Type: text/plain, Size: 352 bytes --]
From what I can tell, FOLDERS is where the defaults are derived from in a
lot of places, so I want to leave that alone.
I can't actually find get_tests_for_patchset.py anywhere in the DTS repos,
which leads me to believe that it was never actually applied to DTS.
As for comments/documentation, I'll submit a V2 fixing as much of that as I
can find.
[-- Attachment #2: Type: text/html, Size: 435 bytes --]
next prev parent reply other threads:[~2022-01-18 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 15:59 ohilyard
2022-01-17 12:11 ` Juraj Linkeš
2022-01-18 15:21 ` Owen Hilyard [this message]
2022-01-18 15:34 ` [PATCH v2] " ohilyard
2022-01-25 2:39 ` Dong, JunX
2022-01-25 6:20 ` Tu, Lijuan
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='CAHx6DYDv6pN7R+8nVVu5H9xtabfxMQ0_ZoHEEZ=-hCgUzr=k2w@mail.gmail.com' \
--to=ohilyard@iol.unh.edu \
--cc=dts@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--cc=lijuan.tu@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).