From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Dmitry Kozlyuk <dkozlyuk@oss.nvidia.com>, dev <dev@dpdk.org>,
ci@dpdk.org
Subject: Re: [dpdk-ci] [dpdk-dev] [PATCH v6 0/3] eal: add memory pre-allocation from existing files
Date: Mon, 11 Oct 2021 17:12:45 -0400 [thread overview]
Message-ID: <CAOE1vsMiK_w+3x08TSb3xTi_CjspWTokTQXd5yFgSJNhgY29Dw@mail.gmail.com> (raw)
In-Reply-To: <2132581.gUyNG9Hos0@thomas>
[-- Attachment #1: Type: text/plain, Size: 734 bytes --]
Hi All,
I'm assuming this should be added to the "checkpatch" job / report?
Correct, or do folks feel this should be a separate run / report?
Cheers,
Lincoln
On Mon, Oct 11, 2021 at 2:52 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> 11/10/2021 10:56, Dmitry Kozlyuk:
> > v6: fix copyright line (Thomas), add SPDX header for the new test file
> > (BTW, why didn't the CI complain in previous versions?)
>
> Probably because the CI doesn't run the script devtools/check-spdx-tag.sh
> Cc ci@dpdk.org to add this test.
>
>
>
>
--
*Lincoln Lavoie*
Principal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu>
[-- Attachment #2: Type: text/html, Size: 2089 bytes --]
next prev parent reply other threads:[~2021-10-11 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210921081632.858873-1-dkozlyuk@nvidia.com>
[not found] ` <20211011085644.2716490-1-dkozlyuk@nvidia.com>
2021-10-11 18:52 ` Thomas Monjalon
2021-10-11 21:12 ` Lincoln Lavoie [this message]
2021-10-12 6:54 ` Thomas Monjalon
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=CAOE1vsMiK_w+3x08TSb3xTi_CjspWTokTQXd5yFgSJNhgY29Dw@mail.gmail.com \
--to=lylavoie@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=dkozlyuk@oss.nvidia.com \
--cc=thomas@monjalon.net \
/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).