All of lore.kernel.org
 help / color / mirror / Atom feed
From: klaus.goger at theobroma-systems.com <klaus.goger@theobroma-systems.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] sunxi: allow CONFIG_DEFAULT_FDT_FILE override
Date: Thu, 31 May 2018 20:15:50 +0200	[thread overview]
Message-ID: <8378D51C-2DE2-4735-9223-DD270C409BF3@theobroma-systems.com> (raw)
In-Reply-To: <13fb068e-2397-a8d4-0272-0749c0316c6f@xevo.com>

Hi Martin,

> On 31.05.2018, at 19:49, Martin Kelly <mkelly@xevo.com> wrote:
> 
> On 05/23/2018 11:34 AM, Martin Kelly wrote:
>> On 05/17/2018 05:01 AM, Maxime Ripard wrote:
>>> On Tue, May 01, 2018 at 05:46:41PM -0700, Martin Kelly wrote:
>>>> Currently, sunxi-common.h ignores CONFIG_DEFAULT_FDT_FILE and assumes
>>>> the kernel fdtfile and the u-boot devicetree names are the same.
>>>> Although this is typically the case, sometimes you might want to
>>>> customize one of these differently, so it's useful to allow them to be
>>>> different.
>>>> 
>>>> Add logic in sunxi-common.h to respect CONFIG_DEFAULT_FDT_FILE, if set,
>>>> and default to the values it currently uses.
>>>> 
>>>> Signed-off-by: Martin Kelly <mkelly@xevo.com>
>>> 
>>> Acked-by: Maxime Ripard <maxime.ripard@bootlin.com>
>>> 
>>> Maxime
>>> 
>> (ping)
> 
> (ping again)
> 
> Can we get this patch merged?

The else branch will never be selected.
CONFIG_DEFAULT_FDT_FILE will be set to “” if not set by your defconfig.

  reply	other threads:[~2018-05-31 18:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02  0:46 [U-Boot] [PATCH] sunxi: allow CONFIG_DEFAULT_FDT_FILE override Martin Kelly
2018-05-17 12:01 ` Maxime Ripard
2018-05-23 18:34   ` Martin Kelly
2018-05-31 17:49     ` Martin Kelly
2018-05-31 18:15       ` klaus.goger at theobroma-systems.com [this message]
2018-05-31 19:48         ` Martin Kelly
2018-05-31 19:58           ` klaus.goger at theobroma-systems.com
2018-05-31 20:02             ` Martin Kelly
2018-06-01  9:29               ` Jagan Teki
2018-05-31 18:13   ` Jagan Teki
2018-05-31 18:14     ` Martin Kelly

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=8378D51C-2DE2-4735-9223-DD270C409BF3@theobroma-systems.com \
    --to=klaus.goger@theobroma-systems.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.