Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Matyukevich <geomatsi@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] nanpi_neo4_config: Enable BR2_TARGET_ARM_TRUSTED_FIRMWARE_NEEDS_ARM32_TOOLCHAIN optiony
Date: Mon, 30 Mar 2020 18:25:07 +0300	[thread overview]
Message-ID: <20200330152507.GA518052@curiosity> (raw)
In-Reply-To: <1585574086-28047-2-git-send-email-marek.belisko@open-nandra.com>

> Signed-off-by: Marek Belisko <marek.belisko@open-nandra.com>
> ---
>  configs/nanopi_neo4_defconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/configs/nanopi_neo4_defconfig b/configs/nanopi_neo4_defconfig
> index 0e58aea..2bffe66 100644
> --- a/configs/nanopi_neo4_defconfig
> +++ b/configs/nanopi_neo4_defconfig
> @@ -11,6 +11,7 @@ BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_GIT=y
>  BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_URL="https://github.com/ARM-software/arm-trusted-firmware"
>  BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="v2.0"
>  BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="rk3399"
> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_NEEDS_ARM32_TOOLCHAIN=y
>  BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL31=y

I would suggest to write proper commit messages for these two patches.

Otherwise neo4 build looks good:
Tested-by: Sergey Matyukevich <geomatsi@gmail.com>

Regards,
Sergey

  reply	other threads:[~2020-03-30 15:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30 13:14 [Buildroot] [PATCH 1/2] Revert "configs/nanopi_neo4: remove defconfig" Marek Belisko
2020-03-30 13:14 ` [Buildroot] [PATCH 2/2] nanpi_neo4_config: Enable BR2_TARGET_ARM_TRUSTED_FIRMWARE_NEEDS_ARM32_TOOLCHAIN option Marek Belisko
2020-03-30 15:25   ` Sergey Matyukevich [this message]
2020-03-30 16:38     ` [Buildroot] [PATCH 2/2] nanpi_neo4_config: Enable BR2_TARGET_ARM_TRUSTED_FIRMWARE_NEEDS_ARM32_TOOLCHAIN optiony Belisko Marek

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=20200330152507.GA518052@curiosity \
    --to=geomatsi@gmail.com \
    --cc=buildroot@busybox.net \
    /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