From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org, Simon Glass <sjg@chromium.org>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Ahmad Fatoum <a.fatoum@pengutronix.de>,
Nicolas Schier <nicolas@fjasle.eu>,
Jonathan Corbet <corbet@lwn.net>,
Nathan Chancellor <nathan@kernel.org>,
Nick Terrell <terrelln@fb.com>,
linux-doc@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, workflows@vger.kernel.org
Subject: Re: [PATCH v12 0/2] arm64: Add a build target for Flat Image Tree
Date: Fri, 12 Apr 2024 17:06:42 +0100 [thread overview]
Message-ID: <171293331329.145753.1710092313353102300.b4-ty@kernel.org> (raw)
In-Reply-To: <20240329032836.141899-1-sjg@chromium.org>
On Fri, 29 Mar 2024 16:28:34 +1300, Simon Glass wrote:
> Flat Image Tree (FIT) is a widely used file format for packaging a
> kernel and associated devicetree files[1]. It is not specific to any
> one bootloader, as it is supported by U-Boot, coreboot, Linuxboot,
> Tianocore and Barebox.
>
> This series adds support for building a FIT as part of the kernel
> build. This makes it easy to try out the kernel - just load the FIT
> onto your tftp server and it will run automatically on any supported
> arm64 board.
>
> [...]
Applied to arm64 (for-next/kbuild), thanks!
[1/2] arm64: Add BOOT_TARGETS variable
https://git.kernel.org/arm64/c/0dc1670bd0ce
[2/2] arm64: boot: Support Flat Image Tree
https://git.kernel.org/arm64/c/7a23b027ec17
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2024-04-12 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 3:28 [PATCH v12 0/2] arm64: Add a build target for Flat Image Tree Simon Glass
2024-03-29 3:28 ` [PATCH v12 2/2] arm64: boot: Support " Simon Glass
2024-03-29 10:00 ` Masahiro Yamada
2024-04-12 16:06 ` Will Deacon [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=171293331329.145753.1710092313353102300.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=a.fatoum@pengutronix.de \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=sjg@chromium.org \
--cc=terrelln@fb.com \
--cc=workflows@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).