From: Julien Grall <julien@xen.org>
To: Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org
Cc: wl@xen.org, jbeulich@suse.com, george.dunlap@citrix.com,
andrew.cooper3@citrix.com, bertrand.marquis@arm.com,
Volodymyr_Babchuk@epam.com, roger.pau@citrix.com,
Stefano Stabellini <stefano.stabellini@amd.com>
Subject: Re: [PATCH v3 1/4] Add SPDX to CODING_STYLE
Date: Sun, 9 Oct 2022 10:33:14 +0100 [thread overview]
Message-ID: <4c07bd2c-fe8c-9a4c-a7f1-33181596249a@xen.org> (raw)
In-Reply-To: <20221008001544.78302-1-sstabellini@kernel.org>
Hi Stefano,
On 08/10/2022 01:15, Stefano Stabellini wrote:
> From: Stefano Stabellini <stefano.stabellini@amd.com>
>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@amd.com>
> ---
> CODING_STYLE | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/CODING_STYLE b/CODING_STYLE
> index 3386ee1d90..5faf274b3a 100644
> --- a/CODING_STYLE
> +++ b/CODING_STYLE
> @@ -14,6 +14,16 @@ explicitly (e.g. tools/libxl/CODING_STYLE) but often implicitly (Linux
> coding style is fairly common). In general you should copy the style
> of the surrounding code. If you are unsure please ask.
>
> +SPDX
> +----
> +
> +New files should start with a single-line SPDX comment to express the
> +license, e.g.:
> +
> +/* SPDX-License-Identifier: GPL-2.0 */
> +
> +See LICENSES/ for a list of licenses and SPDX tags currently used.
This directory doesn't yet exist. As Jan wrote in v2, this should be
populated first (i.e. patch #2 should be before patch #1).
Cheers,
--
Julien Grall
next prev parent reply other threads:[~2022-10-09 9:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 0:15 [PATCH v3 0/4] introduce SPDX Stefano Stabellini
2022-10-08 0:15 ` [PATCH v3 1/4] Add SPDX to CODING_STYLE Stefano Stabellini
2022-10-09 9:33 ` Julien Grall [this message]
2022-10-09 9:35 ` Julien Grall
2022-10-08 0:15 ` [PATCH v3 2/4] Add licenses under LICENSES Stefano Stabellini
2022-10-09 9:37 ` Julien Grall
2022-10-08 0:15 ` [PATCH v3 3/4] add SPDX to arch/arm/*.c Stefano Stabellini
2022-10-09 9:44 ` Julien Grall
2022-10-08 0:15 ` [PATCH v3 4/4] Remove extra copies of licenses and license headers Stefano Stabellini
2022-10-09 10:14 ` Julien Grall
2022-10-11 0:26 ` Stefano Stabellini
2022-10-11 11:03 ` Julien Grall
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=4c07bd2c-fe8c-9a4c-a7f1-33181596249a@xen.org \
--to=julien@xen.org \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=bertrand.marquis@arm.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=stefano.stabellini@amd.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.