From: Aaron Conole <aconole@redhat.com>
To: Manit Mahajan <mmahajan@iol.unh.edu>
Cc: ci@dpdk.org, probb@iol.unh.edu, alialnu@nvidia.com,
Luca Vizzarro <Luca.Vizzarro@arm.com>
Subject: Re: [PATCH] config: adding dts tag for dts path patches
Date: Mon, 07 Oct 2024 11:52:51 -0400 [thread overview]
Message-ID: <f7t4j5nj4fg.fsf@redhat.com> (raw)
In-Reply-To: <20241001170703.30348-1-mmahajan@iol.unh.edu> (Manit Mahajan's message of "Tue, 1 Oct 2024 13:07:03 -0400")
Manit Mahajan <mmahajan@iol.unh.edu> writes:
> DTS provides a check-format script which runs a series of code quality
> checks including formatting, linting, and type-checking using the
> following tools: black, isort, pylama, and mypy. Developers are supposed
> to run this script before submitting their patch series. In CI testing,
> we want to run this formatting script on all patches which modify
> dpdk/dts/* going forward, and submit a new patchwork check named
> dts-check-format. In order to do this, we need to be able to set a tag
> in the patch parser script for all patch series which meet this
> condition. This series adds the dts tag and path assignment to
> config/patch_parser.cfg.
>
> Signed-off-by: Manit Mahajan
> ---
Hi Manit,
FYI, your signed-off-by line is incorrect. It is missing the email
address. I can add it on apply if you are okay with that, but in the
future, it should look like::
Signed-off-by: Manit Mahajan <mmahajan@iol.unh.edu>
Thanks!
> config/patch_parser.cfg | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/config/patch_parser.cfg b/config/patch_parser.cfg
> index 5757f9a..dac3b23 100644
> --- a/config/patch_parser.cfg
> +++ b/config/patch_parser.cfg
> @@ -13,6 +13,7 @@ app = application
> license = documentation
> VERSION = documentation
> build = core
> +dts = dts
>
> # This is an ordered list of the importance of each patch classification.
> # It should be used to determine which classification to use on tools which
> @@ -22,4 +23,5 @@ priority_list =
> core,
> driver,
> application,
> - documentation
> + documentation,
> + dts
next prev parent reply other threads:[~2024-10-07 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 17:07 Manit Mahajan
2024-10-01 17:19 ` Patrick Robb
2024-10-04 14:01 ` Aaron Conole
2024-10-04 17:54 ` Patrick Robb
2024-10-07 12:56 ` Luca Vizzarro
2024-10-07 15:52 ` Aaron Conole [this message]
2024-10-07 15:54 ` 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=f7t4j5nj4fg.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=Luca.Vizzarro@arm.com \
--cc=alialnu@nvidia.com \
--cc=ci@dpdk.org \
--cc=mmahajan@iol.unh.edu \
--cc=probb@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).