From: Luca Ceresoli <luca@lucaceresoli.net>
To: Neal Frager <neal.frager@xilinx.com>, buildroot@buildroot.org
Cc: wesley@sonifex.co.uk, Neal Frager <neal.frager@amd.com>,
giulio.benetti@benettiengineering.com, michal.simek@amd.com,
yann.morin.1998@free.fr
Subject: Re: [Buildroot] [PATCH v2 3/4] configs/zynqmp_kria_kv260_defconfig: add parameters to generate extlinux.conf
Date: Wed, 15 Jun 2022 23:01:27 +0200 [thread overview]
Message-ID: <8874373f-bb66-80a2-e61f-857b4da08d00@lucaceresoli.net> (raw)
In-Reply-To: <20220609140449.210030-3-neal.frager@xilinx.com>
On 09/06/22 16:04, Neal Frager wrote:
> From: Neal Frager <neal.frager@amd.com>
>
> This patch enables the zynqmp_kria_kv260_defconfig to auto-generate the
> extlinux.conf file.
>
> The board/zynqmp/kria/extlinux.conf and board/zynqmp/kria/post-build.sh have
> been removed as they are no longer necessary.
>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
--
Luca
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-06-15 21:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 14:04 [Buildroot] [PATCH v2 1/4] board/zynqmp/post-build.sh: auto-generate extlinux.conf Neal Frager
2022-06-09 14:04 ` [Buildroot] [PATCH v2 2/4] configs/zynqmp_zcu10x_defconfig: add parameters to generate extlinux.conf Neal Frager
2022-06-15 21:01 ` Luca Ceresoli
2022-06-09 14:04 ` [Buildroot] [PATCH v2 3/4] configs/zynqmp_kria_kv260_defconfig: " Neal Frager
2022-06-15 21:01 ` Luca Ceresoli [this message]
2022-06-09 14:04 ` [Buildroot] [PATCH v2 4/4] board/zynqmp/post-build.sh: remove unnecessary if Neal Frager
2022-06-15 21:01 ` Luca Ceresoli
2022-06-15 5:20 ` [Buildroot] [PATCH v2 1/4] board/zynqmp/post-build.sh: auto-generate extlinux.conf Frager, Neal via buildroot
2022-06-15 21:00 ` Luca Ceresoli
2022-06-19 16:47 ` Arnout Vandecappelle
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=8874373f-bb66-80a2-e61f-857b4da08d00@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=neal.frager@xilinx.com \
--cc=wesley@sonifex.co.uk \
--cc=yann.morin.1998@free.fr \
/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.