From: Denys Dmytriyenko <denis@denix.org>
To: v-singh1@ti.com
Cc: meta-ti@lists.yoctoproject.org, reatmon@ti.com
Subject: Re: [meta-ti][scarthgap][PATCH v5] ti-librpmsg-dma: update ti-librpmsg-dma SRCREV & LICENSE
Date: Wed, 29 Oct 2025 16:11:33 -0400 [thread overview]
Message-ID: <20251029201133.GH3125@denix.org> (raw)
In-Reply-To: <20251029060209.707510-1-v-singh1@ti.com>
On Wed, Oct 29, 2025 at 11:32:09AM +0530, Vishnu Singh via lists.yoctoproject.org wrote:
> From: Vishnu Singh <v-singh1@ti.com>
>
> Replace MIT license with TI-TFL to align with TI release policy
> and product requirements. Legal approval: SRAS00013045
> Update scarthgap srcrev and disable 2dfft example from lib build.
>
> License-Update: Replace MIT to TI-TFL license
Sorry to be pedantic and blunt, but that's not the reason, that's tautology.
License-Update tag (and the commit message in general) must answer the "Why?"
question, not the "What?" question. We can all see the "What?" question being
answered by the code change itself. There's no need to repeat that with the
"changing X to Y". You need to explain why you are changing X to Y...
> Signed-off-by: Vishnu Singh <v-singh1@ti.com>
> ---
> Change log:
> v1->v2:
> - Update commit message with license-update
> v2->v3:
> - Update SRCREV (license updated in README)
> v3->v4:
> - Add branch name in patch subject
> v4->v5:
> - Update latest SRCREV
>
> meta-ti-bsp/recipes-ti/ipc/ti-librpmsg-dma_1.0.bb | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/meta-ti-bsp/recipes-ti/ipc/ti-librpmsg-dma_1.0.bb b/meta-ti-bsp/recipes-ti/ipc/ti-librpmsg-dma_1.0.bb
> index b624871d..7600f867 100644
> --- a/meta-ti-bsp/recipes-ti/ipc/ti-librpmsg-dma_1.0.bb
> +++ b/meta-ti-bsp/recipes-ti/ipc/ti-librpmsg-dma_1.0.bb
> @@ -1,9 +1,9 @@
> SUMMARY = "RPMsg DMA shared library"
> -LICENSE = "MIT"
> -LIC_FILES_CHKSUM = "file://LICENSE;md5=744e63d2bb8c6151dcdd97f49aa02c53"
> +LICENSE = "TI-TFL"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=91dc4ee6d125d0aaba4e5bd2fcc50ed3"
>
> -SRC_URI = "git://github.com/TexasInstruments/rpmsg-dma.git;protocol=https;branch=main"
> -SRCREV = "609fd72f458ba56f80d06810509ef88d010d2c03"
> +SRC_URI = "git://github.com/TexasInstruments/rpmsg-dma.git;protocol=https;branch=scarthgap"
> +SRCREV = "153951932925a72346b76d98b2774952c48a82fc"
>
> S = "${WORKDIR}/git"
>
> @@ -11,6 +11,6 @@ inherit cmake
>
> DEPENDS = "ti-rpmsg-char"
>
> -EXTRA_OECMAKE += "-DBUILD_LIB=ON -DBUILD_EXAMPLE=OFF"
> +EXTRA_OECMAKE += "-DBUILD_LIB=ON -DBUILD_AUDIO_OFFLOAD_EXAMPLE=OFF -DBUILD_2DFFT_OFFLOAD_EXAMPLE=OFF"
>
> COMPATIBLE_MACHINE = "^(k3)$"
> --
> 2.50.1
next prev parent reply other threads:[~2025-10-29 20:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 6:02 [meta-ti][scarthgap][PATCH v5] ti-librpmsg-dma: update ti-librpmsg-dma SRCREV & LICENSE vishnu singh
2025-10-29 6:05 ` PRC Automation
2025-10-29 20:11 ` Denys Dmytriyenko [this message]
2025-10-30 3:39 ` Vishnu Singh
2025-10-30 12:57 ` Ryan Eatmon
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=20251029201133.GH3125@denix.org \
--to=denis@denix.org \
--cc=meta-ti@lists.yoctoproject.org \
--cc=reatmon@ti.com \
--cc=v-singh1@ti.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 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.