All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fdt: avoid bad MAKEALL status
Date: Thu, 19 Apr 2012 11:32:43 -0700	[thread overview]
Message-ID: <CAPnjgZ0FoCF9VdrY7kgyVkVyUQ=Z=pD3cBRruNmemDeZnKGnsg@mail.gmail.com> (raw)
In-Reply-To: <20120419182626.648DB202B35@gemini.denx.de>

On Thu, Apr 19, 2012 at 11:26 AM, Wolfgang Denk <wd@denx.de> wrote:
> Dear Simon,
>
> In message <CAPnjgZ1=Q0=T_vZDZD47h3J65FHitO+0giUkX7pUrECYp=BOkQ@mail.gmail.com> you wrote:
>>
>> A patch to fix this has now been accepted to dtc. So if you update dtc
>> you should find this message goes away.
>>
>> 3cbf829 dtc: Remove spurious output on stderr
>
> There are many systems out there in the field which are subject to a
> rigid policy, and only distribution provided packages get provided.
> Many of the "interesting" distributions don't have this fix yet; for
> example, Fedora 16 (dtc-1.3.0-2.fc16.x86_64) or Debian Wheezy
> (device-tree-compiler 1.3.0-2) bundle DTC version 1.3.0, which is not
> fixed yet.
>
> For the sake of those people I would like to apply this patch.

Acked-by: Simon Glass <sjg@chromium.org>

>
> Best regards,
>
> Wolfgang Denk
>
> --
> DENX Software Engineering GmbH, ? ? MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> The number you have dialed is imaginary. Please divide by 0 ?and ?try
> again.

  reply	other threads:[~2012-04-19 18:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19 12:36 [U-Boot] [PATCH] fdt: avoid bad MAKEALL status Wolfgang Denk
2012-04-19 14:16 ` Simon Glass
2012-04-19 18:26   ` Wolfgang Denk
2012-04-19 18:32     ` Simon Glass [this message]
2012-04-21 14:48 ` Wolfgang Denk

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='CAPnjgZ0FoCF9VdrY7kgyVkVyUQ=Z=pD3cBRruNmemDeZnKGnsg@mail.gmail.com' \
    --to=sjg@chromium.org \
    --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 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.