All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Neal Frager via buildroot <buildroot@buildroot.org>
Cc: Neal Frager <neal.frager@amd.com>
Subject: Re: [Buildroot] [PATCH v1 1/1] board/zynqmp/kria/kv260/uboot.fragment: remove unnecessary CONFIG_MULTI_DTB_FIT option
Date: Sun, 13 Nov 2022 21:58:34 +0100	[thread overview]
Message-ID: <20221113215834.00ae7f71@windsurf> (raw)
In-Reply-To: <20221113184933.47232-1-neal.frager@amd.com>

On Sun, 13 Nov 2022 11:49:33 -0700
Neal Frager via buildroot <buildroot@buildroot.org> wrote:

> This patch removes the CONFIG_MULTI_DTB_FIT u-boot option for the
> zynqmp_kria_kv260_defconfig as it is not necessary.  The post build
> kv260.sh creates the proper u-boot.itb without needing this option.
> 
> Signed-off-by: Neal Frager <neal.frager@amd.com>
> ---
>  board/zynqmp/kria/kv260/uboot.fragment | 1 -
>  1 file changed, 1 deletion(-)

I've applied to master, after adding the following to the commit log:

"""
    Fixes:
    
      https://gitlab.com/buildroot.org/buildroot/-/jobs/3310463281
"""

For future patches, it would be nice if you could include such
references if your patch is aimed at fixing a Gitlab CI failure, or an
autobuilder failure. Thanks a lot!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-11-13 20:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-13 18:49 [Buildroot] [PATCH v1 1/1] board/zynqmp/kria/kv260/uboot.fragment: remove unnecessary CONFIG_MULTI_DTB_FIT option Neal Frager via buildroot
2022-11-13 20:58 ` Thomas Petazzoni via buildroot [this message]
2022-11-14  5:20   ` Frager, Neal via buildroot
2022-11-14 13:28   ` Frager, Neal via buildroot
2022-11-14 13:56     ` Frager, Neal via buildroot
2022-11-15 13:14   ` Peter Korsgaard

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=20221113215834.00ae7f71@windsurf \
    --to=buildroot@buildroot.org \
    --cc=neal.frager@amd.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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.