From: Patrick Robb <probb@iol.unh.edu>
To: ci@dpdk.org
Cc: Ferruh Yigit <ferruh.yigit@amd.com>,
Aaron Conole <aconole@redhat.com>,
Ali Alnubani <alialnu@nvidia.com>,
Adam Hassick <ahassick@iol.unh.edu>,
Cody Cheng <ccheng@iol.unh.edu>
Subject: check-meson.py in CI
Date: Tue, 21 May 2024 17:32:47 -0400 [thread overview]
Message-ID: <CAJvnSUDU29z4uyNAQYXsjW4Xa0z2LhxWaGO7R98BZEG0gPROpw@mail.gmail.com> (raw)
Hi all,
Ferruh has requested that we start running the
./devtools/check-meson.py script in CI testing. Questions:
1. Should it be similar to how Ali runs checkpatches.sh, in that it
would have it's own patchwork context (check-meson)? I think the one
difference is that it can run just 1x/series, instead of on each
individual patch file.
2. Who should run it? It would be a simple addition for the community
lab, but if there is some compelling reason for it running alongside
checkpatch, let me know Ali.
Thanks.
next reply other threads:[~2024-05-21 21:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 21:32 Patrick Robb [this message]
2024-05-22 10:17 ` Thomas Monjalon
2024-05-22 15:47 ` Patrick Robb
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=CAJvnSUDU29z4uyNAQYXsjW4Xa0z2LhxWaGO7R98BZEG0gPROpw@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=aconole@redhat.com \
--cc=ahassick@iol.unh.edu \
--cc=alialnu@nvidia.com \
--cc=ccheng@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=ferruh.yigit@amd.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).