public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Please pull u-boot-fdt
Date: Wed, 12 Oct 2016 10:13:58 -0400	[thread overview]
Message-ID: <20161012141358.GG4990@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ0hEk7Ysc8gJUywYz9Kd5c0=QGS14Sb7BvykaCWbspu1A@mail.gmail.com>

On Tue, Oct 11, 2016 at 02:29:01PM -0600, Simon Glass wrote:

> Hi Tom,
> 
> This is mostly syncing up with upstream. I have a few more things to do
> also (some small, some large).
> 
> 
> The following changes since commit f5fd45ff64e28a73499548358e3d1ceda0de7daf:
> 
>   Merge branch 'master' of git://www.denx.de/git/u-boot-imx (2016-10-08
> 09:33:37 -0400)
> 
> are available in the git repository at:
> 
>   git://git.denx.de/u-boot-fdt.git
> 
> for you to fetch changes up to 7f899e436fe1e952950a14df92600d68d55dea5c:
> 
>   libfdt: Drop inlining of fdt_path_offset() (2016-10-11 14:26:46 -0600)
> 

Something in here is breaking my TI J6 Eco platform.  I'll try and kick
a rebase and bisect of just this series later to pinpoint which one is
at fault (I'm testing all of the other stuff that piled up while my
power was out atm).  Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161012/14a52b53/attachment.sig>

  reply	other threads:[~2016-10-12 14:13 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-11 20:29 [U-Boot] Please pull u-boot-fdt Simon Glass
2016-10-12 14:13 ` Tom Rini [this message]
2016-10-12 14:43   ` Simon Glass
2016-10-13  9:43     ` Keerthy
2016-10-13 11:47       ` Keerthy
2016-10-13 12:11         ` Tom Rini
2016-10-13 12:36           ` Simon Glass
2016-10-13 12:38         ` Simon Glass
2016-10-13 12:39           ` Keerthy
2016-10-13 12:43             ` Simon Glass
2016-10-13 14:24   ` Simon Glass
2016-10-13 14:33     ` Tom Rini
2016-10-13 14:38       ` Simon Glass
2016-10-13 14:59     ` Keerthy
2016-10-13 15:08       ` Simon Glass
2016-10-13 15:34         ` Keerthy
  -- strict thread matches above, loose matches on Subject: below --
2019-11-05 12:23 Simon Glass
2019-11-05 23:12 ` Tom Rini
2017-09-15 19:31 Simon Glass
2017-09-17  1:42 ` Tom Rini
2017-05-09 22:53 Simon Glass
2017-05-09 23:59 ` Tom Rini
2017-05-10 14:29   ` Simon Glass
2017-05-19  0:40   ` Simon Glass
2017-04-10 20:52 Simon Glass
2017-04-11 13:18 ` Tom Rini
2017-01-14 17:14 Simon Glass
2017-01-14 20:57 ` Tom Rini
2016-11-25 16:51 Simon Glass
2016-11-25 19:39 ` Simon Glass
2016-11-26 14:25 ` Tom Rini
2016-10-24  3:01 Simon Glass
2016-10-24 15:24 ` Tom Rini
2016-01-22 21:42 Simon Glass
2016-01-23  0:55 ` Tom Rini
2015-10-03 14:45 Simon Glass
2015-10-03 14:50 ` Tom Rini
2015-10-02 14:14 Simon Glass
2015-07-20 14:04 Simon Glass
2015-07-21 13:50 ` Tom Rini
2015-06-05 16:08 Simon Glass
2015-06-06 13:27 ` Tom Rini
2015-04-24 15:37 Simon Glass
2015-04-28 14:51 ` Tom Rini
2015-04-10 14:16 Simon Glass
2015-04-10 18:49 ` Tom Rini
2015-02-18 13:09 Simon Glass
2015-02-19  4:09 ` Tom Rini

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=20161012141358.GG4990@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox