From: Denys Dmytriyenko <denys@ti.com>
To: Gowtham Tammana <g-tammana@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [PATCH] ti-gc320-driver: add support for RT kernel
Date: Fri, 23 Dec 2016 21:04:55 -0500 [thread overview]
Message-ID: <20161224020455.GF28380@edge> (raw)
In-Reply-To: <1482428592-7035-1-git-send-email-g-tammana@ti.com>
Can you please make sure you are subscribed to the list and can post w/o
problems - it appears this patch never made it to the list.
--
Denys
On Thu, Dec 22, 2016 at 11:43:12AM -0600, Gowtham Tammana wrote:
> Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
> ---
> recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> 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 9344e30..8ad7e4b 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
> @@ -5,13 +5,13 @@ LIC_FILES_CHKSUM = "file://../LICENSE;md5=78d9818a51b9a8e9bb89dea418bac297"
>
> inherit module
>
> -MACHINE_KERNEL_PR_append = "a"
> +MACHINE_KERNEL_PR_append = "b"
> PR = "${MACHINE_KERNEL_PR}"
>
> # Need to branch out with ${PV} var
> BRANCH = "ti-${PV}-k4.4"
>
> -SRCREV = "7a2b06ad1df46a274336f7ae0e24a9d67e72cd66"
> +SRCREV = "65887c911db495fb66c6847c8b6eadc76c7470f4"
>
> SRC_URI = "git://git.ti.com/graphics/ti-gc320-driver.git;protocol=git;branch=${BRANCH}"
> S = "${WORKDIR}/git/src"
> --
> 1.9.1
>
next parent reply other threads:[~2016-12-24 2:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1482428592-7035-1-git-send-email-g-tammana@ti.com>
2016-12-24 2:04 ` Denys Dmytriyenko [this message]
2016-12-23 20:51 [PATCH] ti-gc320-driver: add support for RT kernel Gowtham Tammana
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=20161224020455.GF28380@edge \
--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.