From: Jason Gunthorpe <jgg@nvidia.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: Selvin Xavier <selvin.xavier@broadcom.com>,
Leon Romanovsky <leon@kernel.org>,
Potnuri Bharat Teja <bharat@chelsio.com>,
Yishai Hadas <yishaih@nvidia.com>,
Michal Kalderon <mkalderon@marvell.com>,
Ariel Elior <aelior@marvell.com>,
Zhu Yanjun <zyjzyj2000@gmail.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH] headers: Remove some left-over license text in include/uapi/rdma/
Date: Mon, 26 Sep 2022 15:21:41 -0300 [thread overview]
Message-ID: <YzHttWsmFSMR8vCY@nvidia.com> (raw)
In-Reply-To: <6b2b69c1eb89a37b95d17a1e866c2e8173c6fd15.1664113175.git.christophe.jaillet@wanadoo.fr>
On Sun, Sep 25, 2022 at 03:39:58PM +0200, Christophe JAILLET wrote:
> There is already a SPDX-License-Identifier tag, so the corresponding
> license text can be removed.
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> Changes in the 2 files under rdma/hfi/ is a bit more than just removing
> the license text. There were some Copyright(c) for GPL and BSD licence.
> I have simplified it to what look logical to me.
> But in case it matters, review with care.
Did you use a script or something to verify that the text being
removed is word for word identical to the text in LICENSES/ ?
I had understood this was the reason the original SPDX conversion left
the license text around?
It looks OK to me, but I didn't check it word for word :)
Is there a reason this series is coming up now around the uapi
headers? Are we doing them all or something?
Jason
next prev parent reply other threads:[~2022-09-26 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 13:39 [PATCH] headers: Remove some left-over license text in include/uapi/rdma/ Christophe JAILLET
2022-09-26 18:21 ` Jason Gunthorpe [this message]
2022-09-26 19:32 ` Christophe JAILLET
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=YzHttWsmFSMR8vCY@nvidia.com \
--to=jgg@nvidia.com \
--cc=aelior@marvell.com \
--cc=bharat@chelsio.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mkalderon@marvell.com \
--cc=selvin.xavier@broadcom.com \
--cc=yishaih@nvidia.com \
--cc=zyjzyj2000@gmail.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).