Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] board: Add nanopi-m1 Support
Date: Wed, 5 Jul 2017 18:17:42 +0200	[thread overview]
Message-ID: <20170705181742.43923a6b@windsurf> (raw)
In-Reply-To: <1499270655-2781-1-git-send-email-chakra@openedev.com>

Hello,

On Wed,  5 Jul 2017 21:34:15 +0530, Chakra Divi wrote:
> Add initial support for nanopi-m1 board
> with below features
> - U-Boot 2017.07-rc1
> - Linux 4.11.5
> - Default packages from buildroot
> 
> Signed-off-by: Chakra Divi <chakra@openedev.com>

I've applied, but there were nonetheless a few things to fix, see below.

> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index 3ae7e5d..bbc5bb8 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -127,6 +127,7 @@ mx53loco_defconfig: *defconfig
>  mx6cubox_defconfig: *defconfig
>  mx6sx_udoo_neo_defconfig: *defconfig
>  mx6udoo_defconfig: *defconfig
> +nanopi_m1_defconfig: *defconfig
>  nanopi_neo_defconfig: *defconfig
>  nexbox_a95x_defconfig: *defconfig
>  nitrogen6sx_defconfig: *defconfig
> @@ -205,28 +206,3 @@ zynq_microzed_defconfig: *defconfig
>  zynq_zc706_defconfig: *defconfig
>  zynq_zed_defconfig: *defconfig
>  zynq_zybo_defconfig: *defconfig
> -tests.core.test_post_scripts.TestPostScripts: *runtime_test
> -tests.core.test_rootfs_overlay.TestRootfsOverlay: *runtime_test
> -tests.core.test_timezone.TestGlibcAllTimezone: *runtime_test
> -tests.core.test_timezone.TestGlibcNonDefaultLimitedTimezone: *runtime_test
> -tests.core.test_timezone.TestNoTimezone: *runtime_test
> -tests.fs.test_ext.TestExt2: *runtime_test
> -tests.fs.test_ext.TestExt2r1: *runtime_test
> -tests.fs.test_ext.TestExt3: *runtime_test
> -tests.fs.test_ext.TestExt4: *runtime_test
> -tests.fs.test_iso9660.TestIso9660Grub2External: *runtime_test
> -tests.fs.test_iso9660.TestIso9660Grub2Internal: *runtime_test
> -tests.fs.test_iso9660.TestIso9660GrubExternal: *runtime_test
> -tests.fs.test_iso9660.TestIso9660GrubInternal: *runtime_test
> -tests.fs.test_iso9660.TestIso9660SyslinuxExternal: *runtime_test
> -tests.fs.test_iso9660.TestIso9660SyslinuxInternal: *runtime_test
> -tests.fs.test_jffs2.TestJffs2: *runtime_test
> -tests.fs.test_squashfs.TestSquashfs: *runtime_test
> -tests.fs.test_ubi.TestUbi: *runtime_test
> -tests.fs.test_yaffs2.TestYaffs2: *runtime_test
> -tests.package.test_dropbear.TestDropbear: *runtime_test
> -tests.package.test_python.TestPythonBase: *runtime_test
> -tests.toolchain.test_external.TestExternalToolchainLinaroArm: *runtime_test
> -tests.toolchain.test_external.TestExternalToolchainSourceryArmv4: *runtime_test
> -tests.toolchain.test_external.TestExternalToolchainSourceryArmv5: *runtime_test
> -tests.toolchain.test_external.TestExternalToolchainSourceryArmv7: *runtime_test

Can you investigate why on your system all those lines were removed? I
believe it's because you don't have python-nose2 and/or python-pexpect
installed. Can you run:

  ./support/testing/run-tests -l

and see what it gives ?

>  N:	Chakra Divi <chakra@openedev.com>
> +F:	board/friendlyarm/nanopi-m1
>  F:	board/olimex/a13_olinuxino
>  F:	board/orangepi/orangepi-plus
> +F:	configs/nanopi_m1_defconfig	

There was a trailing tab here.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-07-05 16:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05 16:04 [Buildroot] [PATCH v3] board: Add nanopi-m1 Support Chakra Divi
2017-07-05 16:17 ` Thomas Petazzoni [this message]
2017-07-07 11:17   ` Chakra D

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=20170705181742.43923a6b@windsurf \
    --to=thomas.petazzoni@free-electrons.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