From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Neal Frager via buildroot <buildroot@buildroot.org>
Cc: luca.ceresoli@bootlin.com, michal.simek@amd.com,
Neal Frager <neal.frager@amd.com>
Subject: Re: [Buildroot] [PATCH v1 1/1] board/zynqmp/kria/kv260/uboot.fragment: move to board/zynqmp/kria
Date: Sun, 11 Dec 2022 17:50:14 +0100 [thread overview]
Message-ID: <20221211175014.445e135f@windsurf> (raw)
In-Reply-To: <20221206155226.54290-1-neal.frager@amd.com>
On Tue, 6 Dec 2022 08:52:26 -0700
Neal Frager via buildroot <buildroot@buildroot.org> wrote:
> This patch moves the board/zynqmp/kria/kv260/uboot.fragment file
> to the board/zynqmp/kria directory. The reason is that this file
> is the same for any kria starter kit and is not specific to the kv260.
> By moving the file, it can be logically re-used with the kr260 when
> support for this starter kit is added to buildroot.
>
> KR260 Starter Kit:
> https://www.xilinx.com/products/som/kria/kr260-robotics-starter-kit.html
>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
> ---
> board/zynqmp/kria/{kv260 => }/uboot.fragment | 0
> configs/zynqmp_kria_kv260_defconfig | 2 +-
> 2 files changed, 1 insertion(+), 1 deletion(-)
> rename board/zynqmp/kria/{kv260 => }/uboot.fragment (100%)
Applied to master, thanks.
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
prev parent reply other threads:[~2022-12-11 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 15:52 [Buildroot] [PATCH v1 1/1] board/zynqmp/kria/kv260/uboot.fragment: move to board/zynqmp/kria Neal Frager via buildroot
2022-12-06 17:22 ` Luca Ceresoli via buildroot
2022-12-11 16:50 ` Thomas Petazzoni via buildroot [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=20221211175014.445e135f@windsurf \
--to=buildroot@buildroot.org \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--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.