From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/3] libfdt: fix bugs
Date: Sat, 18 Jul 2015 12:42:32 -0500 [thread overview]
Message-ID: <1437241352.2993.218.camel@freescale.com> (raw)
In-Reply-To: <CAPnjgZ2J964y=0dRUtTv__8+7dksMK4sjs8HzmpV-Zxcbx0ghg@mail.gmail.com>
On Sat, 2015-07-18 at 08:36 -0600, Simon Glass wrote:
> Hi Scott,
>
> On 14 July 2015 at 12:16, Scott Wood <scottwood@freescale.com> wrote:
> > On Wed, 2015-07-15 at 01:08 +0900, Masahiro Yamada wrote:
> > > This series fixes bugs of libfdt.
> > >
> > > These functions were added by Thierry for U-boot only.
> > > So, we do not send it back to the DTC ML.
> >
> > If they're not part of upstream dtc, why are they in the libfdt directory?
> > Have they been sent upstream but not merged?
> >
> > -Scott
>
> To avoid roadblocks we take patches in libfdt before they are merged
> upstream. I then tidy things up when I see them applied. So sometimes
> we are a little ahead of libfdt for a while. It works out OK since we
> need to sync with upstream regularly anyway.
That's fine, but from what Masahiro said, it sounded like there was no intent
to ever push these to upstream dtc.
-Scott
next prev parent reply other threads:[~2015-07-18 17:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 16:08 [U-Boot] [PATCH v2 0/3] libfdt: fix bugs Masahiro Yamada
2015-07-14 16:08 ` [U-Boot] [PATCH v2 1/3] libfdt: fix description of fdt_get_string() Masahiro Yamada
2015-07-18 14:36 ` Simon Glass
2015-07-20 13:25 ` Simon Glass
2015-07-14 16:08 ` [U-Boot] [PATCH v2 2/3] libfdt: fix error code of fdt_get_string_index() Masahiro Yamada
2015-07-18 14:36 ` Simon Glass
2015-07-20 13:25 ` Simon Glass
2015-07-14 16:08 ` [U-Boot] [PATCH v2 3/3] libfdt: fix error code of fdt_count_strings() Masahiro Yamada
2015-07-18 14:36 ` Simon Glass
2015-07-20 13:25 ` Simon Glass
2015-07-14 18:16 ` [U-Boot] [PATCH v2 0/3] libfdt: fix bugs Scott Wood
2015-07-18 14:36 ` Simon Glass
2015-07-18 17:42 ` Scott Wood [this message]
2015-07-20 2:10 ` Simon Glass
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=1437241352.2993.218.camel@freescale.com \
--to=scottwood@freescale.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