public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 08/11] fdt: Add ft_system_setup() function for system device tree additions
Date: Fri, 24 Oct 2014 14:50:12 -0400	[thread overview]
Message-ID: <20141024185012.GI25506@bill-the-cat> (raw)
In-Reply-To: <1414112337-22735-8-git-send-email-sjg@chromium.org>

On Thu, Oct 23, 2014 at 06:58:54PM -0600, Simon Glass wrote:

> Add an additional function for adding information to the device tree before
> booting. This permits additions which are not board-specific.
> 
> Signed-off-by: Simon Glass <sjg@chromium.org>
> Acked-by: Anatolij Gustschin <agust@denx.de>
[snip]
> @@ -3411,7 +3418,7 @@ FIT uImage format:
>  		to 128 or 256, although it does not have to be power of 2).
>  
>  		default: 4096
> -		
> +
>  		CONFIG_MTD_UBI_BEB_LIMIT
>  		This option specifies the maximum bad physical eraseblocks UBI
>  		expects on the MTD device (per 1024 eraseblocks). If the

Was this the only whitespace thinko in README?  If so, yeah, OK, lets
just fix it, if not, drop it.  Otherwise...

Reviewed-by: Tom Rini <trini@ti.com>

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20141024/3f90b535/attachment.pgp>

  reply	other threads:[~2014-10-24 18:50 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24  0:58 [U-Boot] [PATCH v2 01/11] fdt: Allow ft_board_setup() to report failure Simon Glass
2014-10-24  0:58 ` [U-Boot] [PATCH v2 02/11] fdt: Report failure of ft_board_setup() Simon Glass
2014-10-24 15:15   ` Anatolij Gustschin
2014-10-24 18:05   ` Tom Rini
2014-11-21  3:24     ` Simon Glass
2014-10-24  0:58 ` [U-Boot] [PATCH v2 03/11] fdt: Export the fdt_find_or_add_subnode() function Simon Glass
2014-10-24 16:48   ` Anatolij Gustschin
2014-10-24 18:05   ` Tom Rini
2014-11-21  3:24     ` Simon Glass
2014-10-24  0:58 ` [U-Boot] [PATCH v2 04/11] fdt: Add device tree memory bindings Simon Glass
2014-10-24 18:49   ` Tom Rini
2014-10-24 20:04     ` Simon Glass
2014-10-27 14:24       ` Tom Rini
2014-10-27 18:50         ` Simon Glass
2014-11-12 15:13           ` Simon Glass
2014-11-12 21:42           ` Tom Rini
2014-11-12 22:14             ` Simon Glass
2014-11-20 14:37               ` Tom Rini
2014-11-20 17:42                 ` Simon Glass
2014-12-10  5:31                   ` Simon Glass
2014-10-24  0:58 ` [U-Boot] [PATCH v2 05/11] fdt: Use the correct return types for fdtdec_decode_region() Simon Glass
2014-10-24 18:07   ` Tom Rini
2014-11-21  3:25     ` Simon Glass
2014-10-24  0:58 ` [U-Boot] [PATCH v2 06/11] fdt: Enhance flashmap function to deal with region properties Simon Glass
2014-10-24 18:08   ` Tom Rini
2014-11-21  3:25     ` Simon Glass
2014-10-24  0:58 ` [U-Boot] [PATCH v2 07/11] fdt: Tidy up error handling in image_setup_libfdt() Simon Glass
2014-10-24 18:09   ` Tom Rini
2014-11-21  3:25     ` Simon Glass
2014-10-24  0:58 ` [U-Boot] [PATCH v2 08/11] fdt: Add ft_system_setup() function for system device tree additions Simon Glass
2014-10-24 18:50   ` Tom Rini [this message]
2014-11-13  2:40     ` Simon Glass
2014-11-21  3:25       ` Simon Glass
2014-10-24  0:58 ` [U-Boot] [PATCH v2 09/11] fdt: Change fdt_pack_reg() to static and fix types Simon Glass
2014-10-24 18:49   ` Tom Rini
2014-11-21  3:25     ` Simon Glass
2014-10-24  0:58 ` [U-Boot] [PATCH v2 10/11] fdt: Add a function to decode a named memory region Simon Glass
2014-10-24 18:49   ` Tom Rini
2014-11-21  3:26     ` Simon Glass
2014-10-24  0:58 ` [U-Boot] [PATCH v2 11/11] fdt: Try to use fdt_address_cells()/fdt_size_cells() Simon Glass
2014-10-24 18:49   ` Tom Rini
2014-11-21  3:26     ` Simon Glass
2014-10-24 15:50 ` [U-Boot] [PATCH v2 01/11] fdt: Allow ft_board_setup() to report failure Anatolij Gustschin
2014-10-24 18:04 ` Tom Rini
2014-10-24 19:56   ` Simon Glass
2014-11-21  3:24     ` 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=20141024185012.GI25506@bill-the-cat \
    --to=trini@ti.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