From: Denys Dmytriyenko <denys@ti.com>
To: Jean-Jacques Hiblot <jjhiblot@ti.com>
Cc: meta-arago@arago-project.org
Subject: Re: [morty] linux-libc-headers (4.4 kernel): update to include dma-buf.h export fix
Date: Thu, 21 Sep 2017 15:18:42 -0400 [thread overview]
Message-ID: <20170921191841.GH26843@edge> (raw)
In-Reply-To: <1506000653-15572-1-git-send-email-jjhiblot@ti.com>
JJ,
Thanks. Do you need this in morty or krogoth? I believe this is specific to
krogoth, as morty already has this fix. I can merge to krogoth, if you agree.
On Thu, Sep 21, 2017 at 03:30:53PM +0200, Jean-Jacques Hiblot wrote:
> Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com>
> ---
> .../recipes-kernel/linux-libc-headers/linux-libc-headers_4.4.bbappend | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta-arago-distro/recipes-kernel/linux-libc-headers/linux-libc-headers_4.4.bbappend b/meta-arago-distro/recipes-kernel/linux-libc-headers/linux-libc-headers_4.4.bbappend
> index 7d0537d..c1d8fd1 100644
> --- a/meta-arago-distro/recipes-kernel/linux-libc-headers/linux-libc-headers_4.4.bbappend
> +++ b/meta-arago-distro/recipes-kernel/linux-libc-headers/linux-libc-headers_4.4.bbappend
> @@ -1,7 +1,7 @@
> -PR_append = ".arago0"
> +PR_append = ".arago1"
>
> BRANCH = "ti-lsk-linux-4.4.y"
> -SRCREV = "6580f85400b48d55d06f11d6b75c056399123a72"
> +SRCREV = "2612ef5805db717f9818f06786e863d3b1a7f87e"
>
> KERNEL_GIT_URI = "git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git"
> KERNEL_GIT_PROTOCOL = "git"
> --
> 1.9.1
>
next prev parent reply other threads:[~2017-09-21 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 13:30 [morty] linux-libc-headers (4.4 kernel): update to include dma-buf.h export fix Jean-Jacques Hiblot
2017-09-21 19:18 ` Denys Dmytriyenko [this message]
2017-09-22 7:08 ` Jean-Jacques Hiblot
2017-09-22 18:52 ` Denys Dmytriyenko
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=20170921191841.GH26843@edge \
--to=denys@ti.com \
--cc=jjhiblot@ti.com \
--cc=meta-arago@arago-project.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.