From: Denys Dmytriyenko <denys@ti.com>
To: Gowtham Tammana <g-tammana@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [master][PATCH] ti-gc320-driver: move to k4.19
Date: Wed, 20 Feb 2019 17:16:10 -0500 [thread overview]
Message-ID: <20190220221609.GC11501@beryl> (raw)
In-Reply-To: <20190218231230.14092-1-g-tammana@ti.com>
On Mon, Feb 18, 2019 at 05:12:30PM -0600, Gowtham Tammana wrote:
> - Updated the recipe to pick sources for k4.19
> - Removed the gcc8 workaround patch as the new srcrev include those fixes
>
> Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
> ---
...
> diff --git a/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb b/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> index 1a6bc5da..551a3512 100644
> --- a/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> +++ b/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> @@ -9,12 +9,11 @@ MACHINE_KERNEL_PR_append = "e"
> PR = "${MACHINE_KERNEL_PR}"
>
> # Need to branch out with ${PV} var
> -BRANCH = "ti-${PV}-k4.14"
> +BRANCH = "ti-${PV}-k4.19"
>
> -SRCREV = "a36799d9329efcfff19e30e690156d5ebf7e0c55"
> +SRCREV = "9b59e596b4adefabbb686ce8845edef8114558fd"
>
> -SRC_URI = "git://git.ti.com/graphics/ti-gc320-driver.git;protocol=git;branch=${BRANCH} \
> - file://0001-Kbuild-bypass-gcc8-stringop-overflow-error.patch;striplevel=2"
> +SRC_URI = "git://git.ti.com/graphics/ti-gc320-driver.git;protocol=git;branch=${BRANCH}
This change lost the closing quote in SRC_URI, leading to parse errors.
Please at least build-test your patches before submitting them! Thanks.
> S = "${WORKDIR}/git/src"
>
> --
> 2.20.1
>
next prev parent reply other threads:[~2019-02-20 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 23:12 [master][PATCH] ti-gc320-driver: move to k4.19 Gowtham Tammana
2019-02-20 22:16 ` Denys Dmytriyenko [this message]
2019-02-21 0:15 ` Tammana, Gowtham
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=20190220221609.GC11501@beryl \
--to=denys@ti.com \
--cc=g-tammana@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.