All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karthik Ramanan <a0393906@ti.com>
To: "Dmytriyenko, Denys" <denys@ti.com>,
	"R, Karthik" <karthik.ramanan@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [PATCH 1/2] ipumm-fw: Update SRCREV
Date: Fri, 16 Dec 2016 22:45:57 +0530	[thread overview]
Message-ID: <5854214D.7040901@ti.com> (raw)
In-Reply-To: <012b8cea-868d-4c7c-8477-f4428f88323f@email.android.com>

[-- Attachment #1: Type: text/plain, Size: 3005 bytes --]

No. It doesn't. Double checked the license type between the old and new 
and it is the same.

Regards
Karthik

On 16-Dec-16 10:42 PM, Dmytriyenko, Denys wrote:
> Does that change the overall license in any way?
>
> On Dec 16, 2016 12:10, "R, Karthik" <karthik.ramanan@ti.com> wrote:
>
>     Hi Denys,
>
>     The license file has changed to reflect the addition of the new
>     MJPEG Encoder.
>     There is no other change apart from that.
>
>     Let me know if I need to submit the v2 of the patch with the
>     expanded description.
>
>     Regards
>     Karthik
>
>     On 16-Dec-16 10:17 PM, Dmytriyenko, Denys wrote:
>
>         Please briefly explain in the description the change in
>         license checksum and where it affects the license itself. Thanks.
>
>         On Dec 16, 2016 11:44, "R, Karthik" <karthik.ramanan@ti.com>
>         <mailto:karthik.ramanan@ti.com> wrote:
>
>             This will include the following updates:
>              * Addition of MJPEG Encoder
>              * minor bug fixes
>              * codec updates for mpeg2d
>
>             Signed-off-by: Karthik Ramanan <a0393906@ti.com>
>             <mailto:a0393906@ti.com>
>             ---
>              recipes-bsp/ipumm-fw/ipumm-fw_git.bb |    6 +++---
>              1 file changed, 3 insertions(+), 3 deletions(-)
>
>             diff --git a/recipes-bsp/ipumm-fw/ipumm-fw_git.bb
>             b/recipes-bsp/ipumm-fw/ipumm-fw_git.bb
>             index 4bebc2a..85dfc26 100644
>             --- a/recipes-bsp/ipumm-fw/ipumm-fw_git.bb
>             +++ b/recipes-bsp/ipumm-fw/ipumm-fw_git.bb
>             @@ -9,7 +9,7 @@ python __anonymous() {
>              DESCRIPTION = "Firmware for IPU for supporting
>             Accelerated MM decode and encode"
>              LICENSE = "TI-TSPA"
>
>             -LIC_FILES_CHKSUM =
>             "file://Texas_Instruments_ipumm_Manifest.pdf;md5=e3e7d6efc7aca87789775198c4ca9f8e"
>             +LIC_FILES_CHKSUM =
>             "file://Texas_Instruments_ipumm_Manifest.pdf;md5=5cc572579f07af266ab57fc17d762c7f"
>
>              COMPATIBLE_MACHINE = "dra7xx"
>
>             @@ -17,12 +17,12 @@ RDEPENDS_${PN} = " libdce"
>
>              SRC_URI = "git://git.ti.com/ivimm/ipumm.git;protocol=git"
>
>             -SRCREV = "cd93550ed32c7849de91288e7d90cba3bd89614b"
>             +SRCREV = "42fd71596b161e79e017e00741433e84705a28a6"
>
>              S = "${WORKDIR}/git"
>
>              PV = "3.00.12.00"
>             -PR = "r0"
>             +PR = "r1"
>
>              require recipes-ti/includes/ti-paths.inc
>              require recipes-ti/includes/ti-staging.inc
>             -- 
>             1.7.9.5
>
>             -- 
>             _______________________________________________
>             meta-ti mailing list
>             meta-ti@yoctoproject.org <mailto:meta-ti@yoctoproject.org>
>             https://lists.yoctoproject.org/listinfo/meta-ti
>
>
>
>


[-- Attachment #2: Type: text/html, Size: 6322 bytes --]

  reply	other threads:[~2016-12-16 17:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-16 17:12 [PATCH 1/2] ipumm-fw: Update SRCREV Dmytriyenko, Denys
2016-12-16 17:15 ` Karthik Ramanan [this message]
2016-12-16 17:36   ` Denys Dmytriyenko
  -- strict thread matches above, loose matches on Subject: below --
2016-12-16 16:47 Dmytriyenko, Denys
2016-12-16 17:10 ` Karthik Ramanan
2016-12-16 14:46 Karthik Ramanan

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=5854214D.7040901@ti.com \
    --to=a0393906@ti.com \
    --cc=denys@ti.com \
    --cc=karthik.ramanan@ti.com \
    --cc=meta-ti@yoctoproject.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.