From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Thomas Monjalon" <thomas@monjalon.net>, <dev@dpdk.org>
Cc: "Jerin Jacob" <jerinj@marvell.com>,
"Nithin Dabilpuram" <ndabilpuram@marvell.com>,
"Kiran Kumar K" <kirankumark@marvell.com>,
"Sunil Kumar Kori" <skori@marvell.com>,
"Satha Rao" <skoteshwar@marvell.com>,
"Harman Kalra" <hkalra@marvell.com>,
"Christian Koue Muf" <ckm@napatech.com>,
"Serhii Iliushyk" <sil-plv@napatech.com>,
"Rosen Xu" <rosen.xu@altera.com>,
"David Christensen" <drc@linux.ibm.com>,
"Konstantin Ananyev" <konstantin.ananyev@huawei.com>,
"Bibo Mao" <maobibo@loongson.cn>,
"Stanisław Kardach" <stanislaw.kardach@gmail.com>,
"Sun Yuechi" <sunyuechi@iscas.ac.cn>,
"Jiayu Hu" <hujiayu.hu@foxmail.com>,
"Vladimir Medvedkin" <vladimir.medvedkin@intel.com>,
"Bruce Richardson" <bruce.richardson@intel.com>,
"Cristian Dumitrescu" <cristian.dumitrescu@intel.com>
Subject: RE: [PATCH 1/1] move SPDX tag on the first line
Date: Fri, 31 Oct 2025 15:55:27 +0100 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35F65525@smartserver.smartshare.dk> (raw)
In-Reply-To: <20251031142018.49319-1-thomas@monjalon.net>
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Friday, 31 October 2025 15.20
>
> From "Contributor's Guidelines":
> "
> DPDK uses first line of the file to be SPDX tag.
> In case of #! scripts, SPDX tag can be placed in 2nd line of the file.
> "
>
> Some .c or .h files had the SPDX identifier on the second line
> for no good reason, so it is moved to the first line
> to comply with the guidelines.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
Cleaning up is always good.
Acked-by: Morten Brørup <mb@smartsharesystems.com>
prev parent reply other threads:[~2025-10-31 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 14:20 Thomas Monjalon
2025-10-31 14:55 ` Morten Brørup [this message]
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=98CBD80474FA8B44BF855DF32C47DC35F65525@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=bruce.richardson@intel.com \
--cc=ckm@napatech.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=drc@linux.ibm.com \
--cc=hkalra@marvell.com \
--cc=hujiayu.hu@foxmail.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=konstantin.ananyev@huawei.com \
--cc=maobibo@loongson.cn \
--cc=ndabilpuram@marvell.com \
--cc=rosen.xu@altera.com \
--cc=sil-plv@napatech.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.com \
--cc=stanislaw.kardach@gmail.com \
--cc=sunyuechi@iscas.ac.cn \
--cc=thomas@monjalon.net \
--cc=vladimir.medvedkin@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).