From: Denys Dmytriyenko <denys@ti.com>
To: Dan Murphy <dmurphy@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [PATCH 1/2] u-boot-ti-staging: update to ti2018.02-rc3 tag
Date: Tue, 3 Jul 2018 14:23:16 -0400 [thread overview]
Message-ID: <20180703182316.GE16981@beryl> (raw)
In-Reply-To: <e17e0b85-3da5-52a8-6fd5-5d2d61d9a93c@ti.com>
Build breakage - seems to be some sort of race...
On Tue, Jul 03, 2018 at 01:04:30PM -0500, Dan Murphy wrote:
> Breaks the build or breaks the boot because this built fine for the uBoot compilation job.
>
> Dan
>
> On 07/03/2018 01:01 PM, Denys Dmytriyenko wrote:
> > This breaks at least am57xx now - I'm investigating...
> >
> >
> > On Tue, Jul 03, 2018 at 11:07:35AM -0500, Dan Murphy wrote:
> >> Signed-off-by: Dan Murphy <dmurphy@ti.com>
> >> ---
> >> recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb | 4 ++--
> >> 1 file changed, 2 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb b/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
> >> index fc0a10e7..33110c1b 100644
> >> --- a/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
> >> +++ b/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
> >> @@ -1,7 +1,7 @@
> >> require u-boot-ti.inc
> >>
> >> -PR = "r13"
> >> +PR = "r14"
> >>
> >> BRANCH = "ti-u-boot-2018.01"
> >>
> >> -SRCREV = "e1183b1ef6a3dc5d54603f904307bdbae51f22c3"
> >> +SRCREV = "d87d0db0acc533e7f9d2711b9cbe1548c7eb9cf9"
> >> --
> >> 2.17.0.582.gccdcbd54c
> >>
>
>
> --
> ------------------
> Dan Murphy
prev parent reply other threads:[~2018-07-03 18:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 16:07 [PATCH 1/2] u-boot-ti-staging: update to ti2018.02-rc3 tag Dan Murphy
2018-07-03 16:07 ` [PATCH 2/2] inux-ti-staging: update " Dan Murphy
2018-07-03 18:01 ` [PATCH 1/2] u-boot-ti-staging: update to " Denys Dmytriyenko
2018-07-03 18:04 ` Dan Murphy
2018-07-03 18:23 ` Denys Dmytriyenko [this message]
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=20180703182316.GE16981@beryl \
--to=denys@ti.com \
--cc=dmurphy@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.