From: Bjorn Andersson <andersson@kernel.org>
To: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH v2 3/5] remoteproc: add SPDX-License-Identifier tag to remoteproc.h
Date: Thu, 30 Jul 2026 21:49:42 -0500 [thread overview]
Message-ID: <amwNE675wplIYEy2@baldur> (raw)
In-Reply-To: <20260724184132.1878077-4-mukesh.ojha@oss.qualcomm.com>
On Sat, Jul 25, 2026 at 12:11:30AM +0530, Mukesh Ojha wrote:
> Add the missing SPDX-License-Identifier tag consistent with the
> BSD-3-Clause license text already present in the file.
>
Looks like the standard BSD blurb, so I think you should take the
opportunity to replace the blurb with the SPDX header, not "duplicate"
the information.
Please update both patches.
Regards,
Bjorn
> Signed-off-by: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
> ---
> include/linux/remoteproc.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/linux/remoteproc.h b/include/linux/remoteproc.h
> index 9cd0708d5ac9..e6b8fbb0af8e 100644
> --- a/include/linux/remoteproc.h
> +++ b/include/linux/remoteproc.h
> @@ -1,3 +1,4 @@
> +/* SPDX-License-Identifier: BSD-3-Clause */
> /*
> * Remote Processor Framework
> *
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-07-31 2:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 18:41 [PATCH v2 0/5] Misc. RSC table changes Mukesh Ojha
2026-07-24 18:41 ` [PATCH v2 1/5] MAINTAINERS: add rsc_table.h to remoteproc entry Mukesh Ojha
2026-07-24 18:41 ` [PATCH v2 2/5] remoteproc: fix coding style issues in remoteproc.h Mukesh Ojha
2026-07-24 18:41 ` [PATCH v2 3/5] remoteproc: add SPDX-License-Identifier tag to remoteproc.h Mukesh Ojha
2026-07-31 2:49 ` Bjorn Andersson [this message]
2026-07-24 18:41 ` [PATCH v2 4/5] remoteproc: add SPDX-License-Identifier tag to rsc_table.h Mukesh Ojha
2026-07-24 18:41 ` [PATCH v2 5/5] remoteproc: fix OOB read via signed offset in rsc_table_for_each_entry() Mukesh Ojha
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=amwNE675wplIYEy2@baldur \
--to=andersson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mukesh.ojha@oss.qualcomm.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