All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add some missing endian conversions in fdt_support.c
Date: Sun, 13 Nov 2011 12:04:43 -0500	[thread overview]
Message-ID: <4EBFF8AB.1080104@gmail.com> (raw)
In-Reply-To: <1320743132-30994-1-git-send-email-gabeblack@chromium.org>

On 11/08/2011 04:05 AM, Gabe Black wrote:
> Some functions in fdt_support.c use fdt_getprop to read 32 bit values out of
> the device tree, but then use them directly without doing any endian
> conversion. Because they check for a value that doesn't actually appear in
> practice, the functions continued to work even though they're incorrect.
> This change adds the missing conversions.
>
> Signed-off-by: Gabe Black<gabeblack@chromium.org>
> ---
>   common/fdt_support.c |    4 ++--
>   1 files changed, 2 insertions(+), 2 deletions(-)

Applied and requested a bugfix pull.

Thanks,
gvb

      parent reply	other threads:[~2011-11-13 17:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08  9:05 [U-Boot] [PATCH] Add some missing endian conversions in fdt_support.c Gabe Black
2011-11-08 13:47 ` Mike Frysinger
2011-11-13  2:07   ` Gabe Black
2011-11-13 17:04 ` Jerry Van Baren [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=4EBFF8AB.1080104@gmail.com \
    --to=gvb.uboot@gmail.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 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.